Re:When “Progress” Is Backwards
by josephcsible on Monday November 09, 2020 @11:52AM
(#25036731)
Most systems that aren't servers only have one Ethernet adapter, which you used to be able to count on being named eth0. "Predictable" is a huge misnomer. They're stable, sure, but they couldn't be further from predictable.
When you use “kernel names” you’re implicitly relying on the fact that your network cards initialize in the same order on boot which isn’t guaranteed. It’s the same reason you should prefer disk UUIDs over /dev/sda. For a long time sysadmins have used udev to pin eth0, eth1, etc. to specific network interfaces to solve this problem but it’s clunky.
systemd changed this in a very elegant way. The BIOS already assigns fixed names to network devices! If you use those you don’t have to query the device for its MAC to figure out its identity like we do with partuuids and diskuuids. The crazy names come from your vendor — nothing stops them from being eth0 eth1. Dell uses eno1 ens1 and enp0s1 depending on the kind of card.
Now by default network device names are fixed and if you want eth0 eth1 like you’re used to the process hasn’t changed.