Bug 915528 - MAC-based network interface naming with systemd/udev is impossible
Summary: MAC-based network interface naming with systemd/udev is impossible
Keywords:
Status: CLOSED DUPLICATE of bug 896135
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 18
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-26 00:36 UTC by Frantisek Hanzlik
Modified: 2013-02-26 01:02 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-26 01:02:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frantisek Hanzlik 2013-02-26 00:36:38 UTC
Description of problem:
despite of docs at:

https://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames

rules for creating ethN interfaces names based on their MAC addresses did not work, interfaces are named ethX but numbered quite randomly.

Version-Release number of selected component (if applicable):
systemd-197-1.fc18.1.i686
kernel 3.7.9-201.fc18.i686.PAE

How reproducible:
Always: take 2+ NICs to box, write /etc/udev/rules.d/70-persistent-net.rules
according to documentation (my is:

# Bus 01:00.0 - PCI device 0x1969:0x1048 Atheros Attansic L1; atl1:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:8c:93:b5:8d", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# External PCI device 0x8086:0x10d3 Intel CT Desktop Adapter w. 82574L; e1000e:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:69:5f:74", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# External PCI device 0x1186:0x1300 D-Link System Inc DFE-528TX w. RTL8139; 8139too
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:11:63:96:35", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

) and boot system. You can see NICs are numbered quite randomly.

Expected results:
udev in F17 and before could did this fine, why should it be impossible now?

Additional info:
Moreover, it seems as udev support in systemd is broken in other area too: even if '/etc/udev/udev.conf' contains 'udev_log="debug"' (and this anyhow work, as there are additional messages in system log), in log isn't anything about which and how /etc/rules.d/ rules are proceeded - thus their debugging is impossible.

Comment 1 Michal Schmidt 2013-02-26 01:02:10 UTC
(In reply to comment #0)
> https://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming

This describes the naming policy using biosdevname. I don't know if you even have biosdevname installed, but in any case your current udev rules would override it.

> http://www.freedesktop.org/wiki/Software/systemd/
> PredictableNetworkInterfaceNames

This describes the naming policy that will be used in Fedora 19, but it is not enabled in Fedora 18.


A couple of suggestions:

1. Install systemd-197-1.fc18.2, which is soon to reach the updates repository:
https://admin.fedoraproject.org/updates/FEDORA-2013-1590/initscripts-9.42.2-1.fc18,systemd-197-1.fc18.2

2. Change your udev rules to assign interface names that do not collide with the names the kernel itself generates (so no "ethX" names, but perhaps something meaningful like "external", "internal", "red", "green", "dmz", ...).

*** This bug has been marked as a duplicate of bug 896135 ***


Note You need to log in before you can comment on or make changes to this bug.