I think that as long as the udev file for ethernet devices (70
-persistent-net.rules) has right mac addresses it's not a kernel issue,
but udev fault. What's more, if I remove all the references to any
device and restart, udev regenerates this info in the right way.
Restarting several times produces no change, so the configuration is
stable, and even solves bug 148116 (at least my concerns).

It's my fault to not have investigated before, but I'm not udev expert
to have guessed udev behaviour maybe not wise enough to determine
"invalid" or duplicate definitions (maybe already customizable, but in a
wrong logic?). Here's part of my previous udev file, with one built-in
ethernet and a USB ethernet device:

# USB device 0x0b95:0x1720 (asix)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:50:5b:00:b6:67", 
ATTR{type}=="1", NAME="eth2"

# USB device 0x0b95:0x1720 (asix)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:50:5b:00:b6:67", 
ATTR{type}=="1", NAME="eth3"

# USB device 0x0b95:0x1720 (asix)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:50:5b:00:b6:67", 
ATTR{type}=="1", NAME="eth4"

# USB device 0x0b95:0x1720 (asix)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:50:5b:00:b6:67", 
ATTR{type}=="1", NAME="eth5"

# USB device 0x0b95:0x1720 (asix)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:50:5b:00:b6:67", 
ATTR{type}=="1", NAME="eth6"

# USB device 0x0b95:0x1720 (asix)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:50:5b:00:b6:67", 
ATTR{type}=="1", NAME="eth7"


And my built-in ethernet was being named eth8, until I deleted all entries and 
tested automatic configuration from scratch, where it becomes eth0 and this USB 
interface, eth1 (the right values for both).

So, taking the subject for this issue, I don't know why udev, with the
same mac address (a valid mac address), was adding a new entry,
increasing the value and breaking my scripts.

-- 
Ethernet device's number increases by one after every reboot
https://bugs.launchpad.net/bugs/153727
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to