On Thu, Oct 03, 2019 at 03:29:22PM +0200, Michael Biebl wrote: > Am 03.10.19 um 15:23 schrieb Michael Biebl: > > Am 03.10.19 um 15:13 schrieb Andreas Henriksson: > > > >> (Personally while the persistent naming scheme is good, I don't really > >> see the point of it for wifi devices where I don't think anyone should > >> reference them by name anyway. One potential solution I can think of > >> would thus be to disable the scheme for wifi. But I'll just wait and see > >> what others come up with....) > > > > You mean shipping a link file like this: > > > > [Match] > > Type=wlan > > [Link] > > NamePolicy=keep
Possibly that, or modifying the original policy to avoid wifi from the start if possible.... I haven't really looked deeper into this. > > > While testing this, I ran > rmmod iwldvm iwlwifi > modprobe iwlwifi > > My interface is renamed from wlan0 → wlan1 → wlan2 ... > I'm currently at wlan3. > > iwd seems to be interfering here as well. > If I run systemctl stop iwd.service, a rmmod / modprobe results in wlan0. > Can you reproduce the issue? Any idea what's going on there? Yes and AFAIK this happens unrelated to iwd. My suspicion is that the kernel is shit. You can probably reuse the wlan0 name by rubbing the kernel in the right direction before unloading the driver. eg. Try bringing the interface down before rmmod. (Not sure what it takes. Some kernel person might know.) Regards, Andreas Henriksson PS. Would be awesome if this could be cherry-picked for next NM upload: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/285 ;)
