You are not logged in.
Some time ago Predictable Network Interface Names were introduced, for anyone with just one interface eth0 was probably predictable enough but now we have some random jumble of letters and numbers.
If this works then it is just a case of initial set up and forget it, in my case it seems to be more of a problem. Sometimes after a reboot the interface name is different than it was before, network connection is lost of course. The solution seems to be 'ip link' to find out the new name, edit the netctl interface config file, stop the profile, reenable the profile using netctl reenable [profile] and finally netctl start [profile].
I have not found a reproducible way of getting this to happen, it seems somewhat random but I rarely turn the system off so then it just works, it may happen more after system updates but it does happen at other times. Obviously ensuring the name stayed predictable would be preferable to the workaround above, but I have no idea why the name changes, or even what decides the name in the first place.
Offline
You can append net.ifnames=0 to the kernel command line to restore the old behavior. According to http://www.freedesktop.org/wiki/Softwar … faceNames/ it is an udev rule in /usr/lib/udev/rules.d/80-net-setup-link.rules. I guess that in your case there is a race condition between this rule an another network "thing" that has to be done before. I am not competent enough to debug it further though. IMHO, the systemd with its parallelisation is fantastic when it works but very hard to debug when something goes wrong.
Last edited by olive (2014-09-25 06:57:58)
Offline