Control: tags -1 upstream help Hi,
On Thu, Oct 03, 2019 at 12:33:23PM +0200, Michael Biebl wrote: > Package: iwd > Version: 0.21-1 > Severity: normal > > Hi, > > if I use the default persistent naming scheme or a custom interface name > (in my case I tested with the name "wifi0") this seems to fail once iwd > is installed and I get a failure like this during boot: [...] > But somehow iwd re-initializes the interface and then interferes with > the udev renaming. > > This has the potential to break existing configuration which expects the > interface name as setup by the admin. This was recently discussed during the all-systems-go.io talk on iwd during the QA part and I think you'll get a much better description by watching it at https://youtu.be/p7d5iXUU3qE?t=1149 rather than me retelling the story. (Question asked at 19:09) TL;DR iwd is fast(er than udev), doesn't care about interface name(s), brings interface up, udev starts later and tries to rename already up interface. You should be able to work around this by slowing iwd down (eg. by inserting an ExecStartPre sleep 10, or possibly some dependency that makes sure udev gets a chance to rename before iwd starts). This ofcourse has the drawback that you slow iwd down, and presumably it being fast is one of the main reasons to use it. (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....) Regards, Andreas Henriksson
