Bug 673360 – sys-fs/udev-239 network interfaces renamed from enp0s3 to ens3 on virtual machines

• Status: RESOLVED WORKSFORME
• Product: Gentoo Linux

[Description Johannes Hirte 2018-12-17 19:54:34 UTC]

The update from sys-fs/udev-238 to sys-fs/udev-239 breaks network on my systems, because they're renamed from enp0s3 to ens3 on my virtual machines (libvirt/kvm). Downgrading to sys-fs/udev-238 fixed this reliable.

[Comment 1 William Hubbs 2018-12-25 21:50:28 UTC]

Please test with udev-240. If this is still an issue, please report it
upstream [1] and link the issue here.

[1] https://github.com/systemd/systemd/issues/

[Comment 2 Johannes Hirte 2018-12-26 21:26:04 UTC]

With udev-240 it's renamed again, to eth0.

So now we have:

udev-238: enp0s3
udev-239: ens3
udev-240: eth0

This was all tested with linux-4.19.12. The only part that was changed was udev and meson for build-reasons.

[Comment 3 Johannes Hirte 2018-12-26 21:38:11 UTC]

bug reported upstream: https://github.com/systemd/systemd/issues/11277

[Comment 4 Johannes Hirte 2019-01-04 19:02:24 UTC]

According to upstream, the network interface name from udev-238 was buggy. So changing this is right. But since udev-238 shows the wrong behaviour a big warning should be displayed during update. Especially for headless systems it's not acceptable, when the network interface becomes unreachable because of an update.

[Comment 5 Mike Gilbert 2019-01-24 14:58:33 UTC]

The behavior in 239 is correct, and 240 has also been fixed via a backported patch.