Your message dated Wed, 21 Feb 2018 16:21:53 +0100 with message-id <1d407861-de48-2a54-5d66-3082b91a7...@debian.org> and subject line Re: Bug#890986: BIOS upgrade change main ethernet device name / regression from previous debian versions has caused the Debian Bug report #890986, regarding BIOS upgrade change main ethernet device name / regression from previous debian versions to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 890986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: udev Version: 232-25+deb9u1 Severity: normal On a Asrock AB350 Gaming K4 motherboard based machine running debian stretch we upgraded BIOS from P3.00 to P4.60 and this changed the integrated motherboard ethernet device name from enp10s0 to enp37s0. As a consequence we lost network connectivty and had to edit configuration files. Initial BIOS: r8169 0000:0a:00.0 enp10s0: renamed from eth0 New BIOS: r8169 0000:25:00.0 enp37s0: renamed from eth0 On older versions debian /etc/udev/rules.d/70-persistent-net.rules would have made the ethernet device name constant and we would not have lost network connectivity, so the current state of udev is an unfortunate regression. Is there a way to force generation of 70-persistent-net.rules? Thanks in advance, Sincerely, Laurent
--- End Message ---
--- Begin Message ---Am 21.02.2018 um 11:13 schrieb Laurent GUERBY: > Package: udev > Version: 232-25+deb9u1 > Severity: normal > > On a Asrock AB350 Gaming K4 motherboard based machine > running debian stretch we upgraded BIOS from P3.00 to P4.60 and this > changed the integrated motherboard ethernet device name from enp10s0 to > enp37s0. As a consequence we lost network connectivty and had to edit > configuration files. > > Initial BIOS: > r8169 0000:0a:00.0 enp10s0: renamed from eth0 > > New BIOS: > r8169 0000:25:00.0 enp37s0: renamed from eth0 That's very unfortunate, unfortunately we can't really fix that in systemd. > On older versions debian /etc/udev/rules.d/70-persistent-net.rules > would have made the ethernet device name constant and we would > not have lost network connectivity, so the current state of udev is an > unfortunate regression. > > Is there a way to force generation of 70-persistent-net.rules? No, but you can setup your own naming scheme, matching on whatever you see fit, including the MAC address. Say I wanted to name my ethernet device net0, then you could setup something like $ cat /etc/systemd/network/70-net.link [Match] MACAddress=00:11:22:33:44:55:66 [Link] Name=net0 If you are going to rename network interfaces, don't reuse the kernel provided names, i.e. ethX and wlanX, as this is inherently racy. See man systemd.link for more information on this. If you are sure, that your system will only ever have a single network interface, you can also disable the new default network interface naming scheme and use the kernel provided names. See /usr/share/doc/udev/README.Debian.gz → "Network interface naming" Let me repeat: Using the kernel provided names is probably only a good idea if you have a single network interface. With multiple interfaces, you have no guarantee in which order they are enumerated and named. I'm closing this bug report, as unfortunately there is nothing really that systemd/udev can do, if your bios update has such effects. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers