https://bugzilla.novell.com/show_bug.cgi?id=849749 https://bugzilla.novell.com/show_bug.cgi?id=849749#c9 Ralf Friedl <Ralf.Friedl@online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |Ralf.Friedl@online.de InfoProvider|abittner@abittner.de | --- Comment #9 from Ralf Friedl <Ralf.Friedl@online.de> 2014-03-10 15:09:50 UTC --- (In reply to comment #8)
Ok, the systemd folks tried to re-invent the wheel. And they failed like in every other case. ACK What's wrong with MAC-address-based persistent naming? (And use that en* naming as a fall-back...)
I just want to add that I have exactly the same problem. I added an extra network card, and these stupid interface names just changed. Before this, for many years I could be sure that once assigned, the interface names would stay the same, using /etc/udev/rules.d/70-persistent-net.rules. Now I add a new card and all the configuration is messed up. In case the needinfo refers to the readlink commands above, here the output from my system: Mainboard only: /sys/devices/pci0000:00/0000:00:06.0/0000:03:00.0/net/enp3s0 Mainboard and external card, mainboard is now enp4s0: /sys/devices/pci0000:00/0000:00:05.0/0000:03:00.0/net/enp3s0 /sys/devices/pci0000:00/0000:00:06.0/0000:04:00.0/net/enp4s0 Also lspci: Mainboard only: 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 04:06.0 Network controller: AVM GmbH Fritz!PCI v2.0 ISDN (rev 02) Mainboard and external card, mainboard is now enp4s0: 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 05:06.0 Network controller: AVM GmbH Fritz!PCI v2.0 ISDN (rev 02) As you can see, the number is just an enumeration, so the naming is just as unpredictable as before, but with more confusing names. Who wants to remember on a machine with only one interface, whether on a particular machine it is called enp3s0 or enp5s1, when before you could be sure the name was eth0? And for machines with multiple interfaces, we had 70-persistent-net.rules and a network name once assigned never changed. So this change makes nothing better and everything worse. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.