I have a clue to this bug (and also a workaround). I tried changing my rules instead of using eth0 and eth1 to using eth1 and eth2
Basically, I didn't change the declaration of eth1, and moved the one of eth0 to eth2. So now what happens. 83:2C starts first, it gets eth0 (eth1 on udev) then the other gets eth1 (eth2 on udev). Then udev comes and says : [ 19.666153] udev: renamed network interface eth1 to eth2 [ 19.696240] udev: renamed network interface eth0_rename to eth1 If the order is reverse at startup we get : 73:8C starts first and gets eth0 (eth2 on udev) the other gets eth1 (eth1 on udev, this is already OK then) So now udev has only one change to make : [ 19.666153] udev: renamed network interface eth0 to eth2 Problem is (I suppose), when you assign eth0 and eth1 and it started in the reverse order, udev would have to make 3 moves to change the interfaces : [ 19.666153] udev: renamed network interface eth0 to eth0_rename [ 19.696240] udev: renamed network interface eth1 to eth0 [ 19.696240] udev: renamed network interface eth0_rename to eth1 Classic exchange of two variables works in 3 moves. I bet this is why I have an interface that's called now : eth0_rename. Some sort of bug around this exchange might have happened. Well, anyway with eth1 and eth2 it seems to work whichever interface starts first. -- UDEV rules ignored for ethernet (eth*) devices https://bugs.launchpad.net/bugs/592963 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
