From ArchWiki
Jump to: navigation, search

For my system with a Sun Cassini Quad-NIC the command

ip link set dev eth0.100 up

doesn't work, it always says "Network unreachable". I think this has to be

ip link set dev eth0 up

as you have to up the interface, not the VLAN. Tomtom (talk) 20:10, 9 May 2014 (UTC)

Sounds OK to up a VLAN device, but it should probably be created first.
I would try
ip link add link eth0 name eth0.100 type vlan id 100
before the "up".
ip link set dev eth0.100 up
Seems to work with similar commands on my config.
RegisC (talk) 21:24, 11 May 2014 (UTC)

Interface Naming

I think it'd be helpful to replace the interface names (e.g. eth0) with new systemd device names (e.g. wwp0s20u4c2i12). The new names are definitely more verbose, but more accurately reflect the current state of networking on Arch systems. Zeal J. (talk) 16:54, 2 April 2015 (UTC)

I'm neutral on the matter; your argument is sound, but eth0/wlan0 is easy to keep consistent across articles. In either case, pseudo-variables should be added. -- Alad (talk) 18:41, 2 April 2015 (UTC)
In this vein, I somewhat hate the example for setting up vlan's via systemd, since the file names and virtual adapter names (eg, Name= lines) all contain both the real adapter name and the vlan number which I think tends to lead users to think that's required. For example: on my networks, I tend to prefer to give functional names for vlans... So my guest wifi might run on Id=200 with the Name=guest and unit files /etc/systemd/network/*. When I use ip addr it shows up like 5: guest@eno1: <BROADCAST,MULTICAST,UP,LOWER_ ..., so it's easy to see the ethernet adapter used, but the numeric vlan id is not immediately visible. I think making it clear what values are arbitrary (but must match) vs what values that are defined by externalities (your adapter name and switch configuration) would be helpful. But this also seems like a change where others might have strong opinions the other way. Thoughts? Bobpaul (talk) 23:20, 28 March 2018 (UTC)