network interface problem related to udev and eudev

[aeronova]

Hello all,

I need some help with not-running network interfaces after resolving a conflict between udev and eudev. After a fresh installation, I bumped into a blocking issue saying "sys-fs/udev is blocking sys-fs/eudev." So I googled and found a post (https://forums.gentoo.org/viewtopic-t-966786-start-0.html), which says

emerge -Ca udev
emerge -1a eudev
etc-update
emerge @preserved-rebuild

Note that I also recompiled the kernel to enable CONFIG_FHANDLE. Everything went smooth, but after rebooting my system, I found 1) the names of my network interfaces are changed and 2) they are not running. Originally the network interfaces are denoted by enp0s25 and enp6s0, and now they are shown as eth1 and eth0, respectively. What bugs me is none of them is running. I used the installation CD to chroot then install udev again, but still the network devices are not running. I'd appreciate if if someone could help me with this problem.

Best regards.

[wraeth]

When you first built the system, the devices were probably named with the predictable device naming schema used by sys-fs/udev and sys-apps/systemd. When you've changed to sys-fs/eudev, it's fallen back to the traditional device naming.

If you want to revert to using predictable device naming, you need to re-emerge sys-fs/eudev with the 'rule-generator' use flag switched (I think you need to disable it, but I can't remember exactly which way around it is). Once you've done that and rebooted, your network devices will return to their original names and should start at boot.

If you want to keep the legacy device naming scheme, then you need to update your network init scripts to match the different naming by removing the net.<iface> init scripts and recreating them with the new names:

[aeronova]

Thanks for the instructions, wreath!

Somehow I fixed the problem by updating system and world as follows: