*** This bug is a duplicate of bug 1324558 ***
https://bugs.launchpad.net/bugs/1324558
FYI: for working udev rules...
An example from above:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="ac:16:2d:9b:07:4f", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="p3p4"
But I found that using it that way will not fix the case where a device
is randomly named "renameX" on boot.. But if you remove all the optional
bits from the line, it works reliably:
SUBSYSTEM=="net", ATTR{address}=="ac:16:2d:9b:07:4f", NAME="p3p4"
My guess it that it doesn't think the "rename#" ones match the other
criteria. So just use MAC, which is unique.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284043
Title:
udev renaming the same hardware network i/f to different name, breaks
networking and firewall
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/biosdevname/+bug/1284043/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
