Bridged interfaces and VLAN tags
I’m trying to set up a system that joins an untagged Ethernet network to a TAP tunnel, adding a VLAN tag as the traffic moves to the tunnel.
I’m trying to set up a system that joins an untagged Ethernet network to a TAP tunnel, adding a VLAN tag as the traffic moves to the tunnel.
I have a device that I need to connect to over SSH. The device is connected to my workstation via a direct ethernet connection. I’m attempting to assign the connected device an IP address somehow that I can SSH to, however all of the guides I’m finding have the user configure the IP from whatever device they’re working with (namely Raspberry Pi’s and so on). This is not something I can do with this device as I’ve no physical interface to work with.
I am using Raspberry Pi using Raspbian which is just Debian.
We have a RHEL 5.5 box with 8 interfaces. And the eth interface naming is flip flopping. Sometimes eth0 comes up on physical port 7th, and sometimes on another physical port.
I have a problem with an ASUSPRO B8430UA laptop: when I boot it with Ubuntu 16.04 (or NixOS 16.03) the Ethernet port does not work. The driver used is e1000e, it reports:
In Linux, is there any difference between after-ip link down-condition and real link absence (e.g. the switch’s port burned down, or someone tripped over a wire).
By difference I mean some signs in the system that can be used to distinguish these two conditions.
E.g. will routing table be identical in these two cases? Will ethtool or something else show the same things? Is there some tool/utility which can distinguish these conditions?