On Wed, 15.04.15 01:08, Andrew Cooks (aco...@linux.com) wrote: > On Tue, Jan 13, 2015 at 6:46 AM, Jan Engelhardt <jeng...@inai.de> wrote: > > > > > On Monday 2015-01-12 18:29, Tom Gundersen 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? > > > > Well, the manpage states: "All link files are collectively > > sorted and processed in lexical order", with that, I would assume > > that 99a, being processed after 99, would override 99. > > > > >It works for me when naming it 98-ether.link instead. > > > > Not in my case. I have a feeling networkd won't touch > > [08:00:27:0a:c5:b2]'s interface name because it has already > > been named by udev to enp0s3 before networkd got a chance to run. > > Could that be it?
Note that networkd doesn't rename interfaces, only udev does. udev implements .link processing, nothing else. > I'm having a similar problem while running systemd version-219. Did you > work out what was wrong? Maybe this is debian and the saving of interface names is still in place? > # cat /etc/systemd/network/01-mgmt.link > [Match] > Path=pci-0000:01:00.0 > Type=ether > > [Link] > Name=mgmt > MACAddressPolicy=persistent Consider testing the .link file with "udevadm test-builtin net_setup_link..." Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
