Re: is the systemd .link mechanism supposed to work?

2019-07-28 Thread Luca Olivetti
El 28/7/19 a les 14:09, Reco ha escrit: Yes. No. Maybe. These things are called Predictable because they aren't. A modern systemd paradox, if you will. :-D Btw, ln -s /dev/null /etc/systemd/network/99-default.link [*] worked, at least in stretch. I hope that it still works in buster. [*]

Re: is the systemd .link mechanism supposed to work?

2019-07-28 Thread Reco
On Sun, Jul 28, 2019 at 11:04:41AM +0200, Luca Olivetti wrote: > El 27/7/19 a les 23:20, Reco ha escrit: > > > > > > yet it always gets the name wlxe894f615307a. > > > > What you're doing colud work. > > The problem is - you have NIC that's attached via USB, so the usual > > rules do not apply.

Re: is the systemd .link mechanism supposed to work?

2019-07-28 Thread Luca Olivetti
El 27/7/19 a les 23:20, Reco ha escrit: yet it always gets the name wlxe894f615307a. What you're doing colud work. The problem is - you have NIC that's attached via USB, so the usual rules do not apply. The reason of it - /lib/udev/rules.d/73-usb-net-by-mac.rules, that's applied after your

Re: is the systemd .link mechanism supposed to work?

2019-07-27 Thread Reco
Hi. On Sat, Jul 27, 2019 at 08:06:36PM +0200, Luca Olivetti wrote: > No matter what I do, the integrated network port is always named eth0 (with > or without the .link file), while the usb wifi stick always takes the "funny" > name > based on its mac address (wlxe894f615307a). > #

is the systemd .link mechanism supposed to work?

2019-07-27 Thread Luca Olivetti
Hello, I'm preparing to upgrade my linkstation pro from stretch to buster. I'm following the instructions here: https://www.debian.org/releases/buster/armel/release-notes/ch-information.en.html#migrate-interface-names and I'm trying to use .link files in /etc/systemd/network to rename the