Bug 76599

Summary:	RFE: systemd-networkd: persistent mac setup: support devices on the platform bus
Product:	systemd	Reporter:	Damjan Georgievski <gdamjan>
Component:	general	Assignee:	Tom Gundersen <teg>
Status:	RESOLVED NOTABUG	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Damjan Georgievski 2014-03-25 16:13:44 UTC

On the BeagleBoard-xM the ethernet interface is a usb device, using the smsc95xx driver. As I've been told it's connected on the platform bus (see udevadm output below). It doesn't have a hardware mac address, so networkd should provide one. Unfortunately the default MACAddressPolicy=persistent doesn't not configure the same mac address on each boot.

The distro is ArchLinuxArm (armv7l), systemd is 211.



# udevadm info /sys/class/net/eth0
P: /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.1/1-2.1:1.0/net/eth0
E: DEVPATH=/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.1/1-2.1:1.0/net/eth0
E: ID_BUS=usb
E: ID_MODEL=ec00
E: ID_MODEL_ENC=ec00
E: ID_MODEL_FROM_DATABASE=SMSC9512/9514 Fast Ethernet Adapter
E: ID_MODEL_ID=ec00
E: ID_NET_DRIVER=smsc95xx
E: ID_PATH=platform-ehci-omap.0-usb-0:2.1:1.0
E: ID_PATH_TAG=platform-ehci-omap_0-usb-0_2_1_1_0
E: ID_REVISION=0200
E: ID_SERIAL=0424_ec00
E: ID_TYPE=generic
E: ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class
E: ID_USB_DRIVER=smsc95xx
E: ID_USB_INTERFACES=:ff00ff:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=0424
E: ID_VENDOR_ENC=0424
E: ID_VENDOR_FROM_DATABASE=Standard Microsystems Corp.
E: ID_VENDOR_ID=0424
E: IFINDEX=2
E: INTERFACE=eth0
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth0
E: TAGS=:systemd:
E: USEC_INITIALIZED=55755

Comment 1 Tom Gundersen 2014-03-31 20:19:21 UTC

We should probably improve the docs/logging in this case. We do not (and cannot easily) support non-pci devices. We rely entirely on the ID_NET_NAME_* variables to give us persistent data about the device. These are only set for pci devices, so we are sort of at a loss here unless we improve the network device naming logic.

Comment 2 Tom Gundersen 2015-02-06 07:33:09 UTC

I added some more debug output for this case, and also expanded the manpage a bit. I don't see anything else we can do here at the moment, so closing this. Thanks for the report!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.