Bug 518682 – Switch network interface renaming logic to less error prone solution

• Status: RESOLVED FIXED
• Product: [OLD] Docs on www.gentoo.org

[Description Samuli Suominen (RETIRED) 2014-07-31 15:46:32 UTC]

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=2#doc_chap4

[Comment 1 Samuli Suominen (RETIRED) 2014-07-31 15:51:48 UTC]

Switch this content...

# vim /etc/udev/rules.d/76-net-name-use-custom.rules
# First one uses MAC information
SUBSYSTEM=="net", ACTION=="add", ENV{ID_NET_NAME_MAC}=="enxc80aa9429d76", NAME="lan0"
# Second one uses ID_NET_NAME_PATH information
SUBSYSTEM=="net", ACTION=="add", ENV{ID_NET_NAME_PATH}=="enp3s0", NAME="wifi0"

To this content...

# vim /etc/udev/rules.d/70-net-name-use-custom.rules
# First one uses MAC information, and 70- number to be before other net rules
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="c8:0a:a9:42:9d:76", NAME="lan0"

# vim /etc/udev/rules.d/76-net-name-use-custom.rules
# Second one uses ID_NET_NAME_PATH information, and 76- number to be between
# 75-net-*.rules and 80-net-*.rules
SUBSYSTEM=="net", ACTION=="add", ENV{ID_NET_NAME_PATH}=="enp3s0", NAME="wifi0"

[Comment 2 Samuli Suominen (RETIRED) 2014-07-31 15:52:56 UTC]

The latter solution is not optimal because it relies too much upon order number as well as the ID_NET* ENV information to be available
As in, the classical MAC renaming is still the best solution

[Comment 3 Sven Vermeulen (RETIRED) 2014-08-17 16:53:58 UTC]

Thanks, updated