On 17/03/2020 19:51, James M. Pulver wrote: > I mostly hate the new network names, and I generally find that they're > fixing something that was never broken for us, but I imagine there was some > way you could get your eth* interfaces confused on reboot I guess. Strange > that the latest vyos which is a router distro designed for lots of > different interfaces that need to stay consistent through reboots still > uses eth*. The need for this might not be clear. But the old eth* scheme was tied to the MAC address of the interface. This new scheme allows hardware to more clearly define the interface name based on the hardware location and not the interface itself.
The use case is: A server needs to replace a NIC for some reason. The process is to shutdown the server, remove the old interface and insert the new one and boot it up again. And everything should work as before. Using the old eth* schema would require modifying configuration files to configure the replaced interface to use the old configuration. While the new approach fixes this, as the configuration is tied to the mainboard slot the interface is inserted into, not the interface MAC address. This might or might not be useful, depending on your needs. The old eth* approach was easy, because it was short and swift and used since the early days. But I do see the old approach could be a burden to larger data centers. -- kind regards, David Sommerseth