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.
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.