udev ethX renaming problem (2 x e1000e) [14.04]

[Marcus_Wellnitz]

hallo kaz,

I had similar problems with ubuntu 14.04.
My Configuration:
2x onboard (igb) NIC
1x 4-port (e1000e) NIC

After installation there were rules in /etc/udev/rules.d/70-persistent-net.rules for my onbord NICs only. Each reboot the e1000e kernel module did a random renaming (p1p1, p1p2, renamed4, p1p4) or similar.
Even rules (copied from onboard NICs) for the e1000e at /etc/udev/rules.d/70-persistent-net.rules were ignored.
It seems that the e1000e driver could not handle ATTR{address}=="00:30:48:b4:33:df" .
Digging arount for 2 Days I found a solution:

## show udev informations for specific NIC
udevadm info --query=all -a --path='/sys/class/net/eth2'

[...]
looking at parent device [...]
KERNELS=="0000:04:00.0"
[...]

# PCI device 0000:04:00.0 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", KERNELS=="0000:04:00.0", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="?*", NAME="eth3"

* Get Informations for your specific device via /sys/class/net/
* let udevadm taverse down to get the device specific PCI-ID (It's unique for each NIC)
* set udev rules to the device-id instead of MAC-Address.

For me it works like a charm.
This solution is very cool if you have a server farm with lots of similar Hardware. Each server can have the same udev-rules because NICs in the same (Hardware) slot will have the same ethX device.

I don't know which component is buggy. I think it's the e1000e kernelmodule, the udev rules script or a kernel timing problem.

Some good informations will begiven by a blog post of Murat Demirten
http://linux-tips.org/article/73/per...ming-with-udev