Predictable network interface names re-enabled after update on server image
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Ubuntu Pi Flavour Maker |
Undecided
|
Unassigned |
Bug Description
Hello...
We're working with the 16.04 Server (minimal) image here. After initial install, predictable network interface names are disabled as advertised. However, after doing an apt update/upgrade, they return (I'm guessing) do to the recent systemd update.
I see /boot/cmdline.txt still contains "net.ifnames=0 biosdevname=0", but it doesn't seem to have any effect. I've disabled them again by adding an entry via /etc/udev/
I just tested this with a fresh image, booting to verify eth0, then apt update/upgrade and reboot to see eth0 removed and an enx------------ mac based interface in its place.
Thanks!
Ricardo (gizmotemp) wrote : | #1 |
Danilo Falcão (fcon) wrote : | #2 |
Commenting the line worked for me. +1
Changed in ubuntu-pi-flavour-maker: | |
status: | New → Confirmed |
Alistair Buxton (a-j-buxton) wrote : | #3 |
The line no longer exists in that file. It is in 73-usb-
Alistair Buxton (a-j-buxton) wrote : | #4 |
FWIW I'm using the official image, not the one made by the flavour maker.
James (k-james-d) wrote : | #5 |
May not be the "best" answer, but I'm just adding /etc/udev/
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_
And not touching changes made by that packages.
Simon Marchi (simon-marchi) wrote : | #6 |
I built a 16.04 minimal image from the scripts, and had this behaviour too (predictable interface name enabled). Creating the link as follows (and rebooting) reverted to eth0:
ln -s /dev/null /etc/udev/
Source: https:/
Tim Jardim (tcjx14me) wrote : | #8 |
@James Pooton
Your suggestion is the one that worked for me
adding /etc/udev/
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_
The other suggestions did not work for me.
- The name change is more of a nuisance than anything. bringing the adapter up and either requesting a new IP via DHCP or assigning a static IP will also work. Changing functional scripts would be a pain however.
Thanks again all
Tim Jardim
Shuhao (shuhao) wrote : | #9 |
I find that adding the /etc/udev/
The same issue for me. Another topic for rasp forum:https:/
Hello,
after some digging I found the origin of the "problem"
When you make apt-get update/upgrade you will update some packages and one of that packages is the udev.
After the update of udev, it updates the file /lib/udev/ rules.d/ 73-special- net-names. rules adding the following line: =="?[014589cd] :*", IMPORT{ builtin} ="net_id" , NAME="$ env{ID_ NET_NAME_ MAC}"
ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", NAME=="", ATTR{address}
If you comment this line everything will work as before!