On 11/28/21 9:50 AM, Jack wrote:
The network name switch ... is not directly due to eudev vs. udev, but to the "new" ... switch to consistent naming ... so your network is probably something like enp20s2, reflecting which slot your network card is physically in.
Except I've had multiple instances where the supposed to be consistent naming is anything but consistent. I don't know if it was a udev issue or something else. But I've seen the actual address of cards in the system change based on what other cards are added to / removed from the system. It seems as if the motherboard re-configured addressing with the hardware change. E.g. NIC1 in PCIe slot A and NIC2 in PCIe slot C. NIC2 changed from (hypothetical) enp20s2 to enp16s2 when NIC1 was removed from PCIe slot A.
So ... if the new naming scheme isn't consistent, then I'm not going to give it the time of day. I'd rather have the older and simpler inconsistent naming scheme (eth#) vs the newer and more annoying scheme en{po}\d\d{,s}{,1,2,3}.
The epiphany when is aw that the supposedly consistent names weren't was a real son of a REDACTED moment.
I'm pretty sure there is a kernel boot parameter which forces the old way, but can't find it now, as I switched to the new naming with eudev, so switching to udev didn't break anything for me.
As Neil B. pointed out, "net.ifnames=0" is now on all my kernel boot lines (for the above reason).
-- Grant. . . . unix || die
