Hi Jan, On Mon, Jan 12, 2015 at 12:20 AM, Jan Engelhardt <[email protected]> wrote: > > In systemd-218, I have configured the following testcase: > > /etc/systemd/network# ls -al > total 20 > drwxr-xr-x 2 root root 4096 Jan 11 18:14 . > drwxr-xr-x 5 root root 4096 Jan 11 16:23 .. > -rw-r--r-- 1 root root 96 Jan 11 18:14 99a-ether.link
Hm, isn't this just a problem of 99a-ether.link being ordered after 99-default.link? It works for me when naming it 98-ether.link instead. > -rw-r--r-- 1 root root 241 Jan 11 18:12 brd0.network > -rw-r--r-- 1 root root 56 Jan 11 18:12 brg0.netdev > > # cat 99a-ether.link > [Match] > MACAddress=08:00:27:0a:c5:b2 > > [Link] > Description=ethernet_link > Alias=ether0 > Name=ether0 > > # systemctl status -l systemd-networkd > ● systemd-networkd.service - Network Service > Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; > vendor preset: enabled) > Active: active (running) since Sun 2015-01-11 18:14:59 EST; 39s ago > Docs: man:systemd-networkd.service(8) > Main PID: 417 (systemd-network) > Status: "Processing requests..." > CGroup: /system.slice/systemd-networkd.service > └─417 /usr/lib/systemd/systemd-networkd > > Jan 11 18:14:59 jng-sfac systemd-networkd[417]: brg0 : netdev ready > Jan 11 18:14:59 jng-sfac systemd[1]: Started Network Service. > > > Why would it be ignoring the link definition file for ether0? > If I invoke `rmmod e1000; modprobe e1000`, systemctl status has > one extra line to say: > > Jan 11 18:17:52 jng-sfac systemd-networkd[417]: eth0 : renamed to > enp0s3 > > > The L2 address is certainly correct: > > 2: enp0s3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether 08:00:27:0a:c5:b2 brd ff:ff:ff:ff:ff:ff I'm not able to reproduce this with current git. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
