"Predictable network interface names" war auch eine der eher idiotischen Ideen unter #linux Remote #Debian update gemacht, danach Rechner nicht mehr erreichbar
-
@giggls Stand aber in den Release-Notes: https://www.debian.org/releases/stable/release-notes/issues.de.html#network-interface-names-may-change
Für Single-NIC Systeme hat mir das auch schon öfters Kopfschmerzen bereitet, aber mit Bonding oder VLAN spezifische NICs will ich schon predictable names.
-
@giggls Stand aber in den Release-Notes: https://www.debian.org/releases/stable/release-notes/issues.de.html#network-interface-names-may-change
Für Single-NIC Systeme hat mir das auch schon öfters Kopfschmerzen bereitet, aber mit Bonding oder VLAN spezifische NICs will ich schon predictable names.
@cytrinox Das Problem hatte ich noch bei keinem update bisher. Mein Desktop hier zu Hause hat den bug dass eth0 nach irgendeinem Kernelupdate plötzlich wierder eth0 heißt. Hier war der workaround einfach Name=e* beim systemd-networkd.
-
@giggls This came up recently in another thread. It is fairly easy to change the naming policy to something more acceptable by overriding the default link file. Like a lot of systemd changes, I don't think this has been disseminated widely enough and a lot of people are grumpy about the default.
https://www.man7.org/linux/man-pages/man7/systemd.net-naming-scheme.7.html -
@giggls This came up recently in another thread. It is fairly easy to change the naming policy to something more acceptable by overriding the default link file. Like a lot of systemd changes, I don't think this has been disseminated widely enough and a lot of people are grumpy about the default.
https://www.man7.org/linux/man-pages/man7/systemd.net-naming-scheme.7.html@kbm0 I do not care about the actual names. What I do care about is when they suddenly change without changing anything on the hardware. This did never happen back when they where called eth0, eth1, ..
My Desktop here has the additional bug that suddenly eth0 is back at the eth0 name after a recent Debian kernel update. -
@kbm0 I do not care about the actual names. What I do care about is when they suddenly change without changing anything on the hardware. This did never happen back when they where called eth0, eth1, ..
My Desktop here has the additional bug that suddenly eth0 is back at the eth0 name after a recent Debian kernel update.@giggls It is more a consequence of the ways PC hardware has changed over the years (plug and play enumeration vs a static setup) than a flaw in the software. With the old naming, there are systems where you will find that eth0 and eth1 swap places on every boot, and if you have one of those you will prefer the new naming. If you really want stability, choose the mac-based naming and you will get every interface named enx followed by the MAC address.
-
System shared this topic
