Bug#982688: wireless interface name unstable across reboots

[Michael Biebl]

Am 22.02.21 um 15:52 schrieb Yuri D'Elia:
> On Mon, Feb 22 2021, Michael Biebl wrote:
>> iwd will re-initialize your wireless interface when it starts (I think
>> it unloads the firmware or something like that). At that point, both iwd
>> and udevd are running and race against each other and usually iwd wins
>> to claim the device.
> 
> I was about to clarify the question regarding the devices above (my
> question was more specific to how devices events are synthesized when
> interface renaming is involved), but this tidbit actually clarifies the
> issue.
> 
> Thing is, I've actually been using UseDefaultInterface=true in iwd.conf
> as well. So, in this case, does the race actually exist?

I have no idea what UseDefaultInterface=true does.

> So talking in general terms, and without requiring the admin to list
> specific interfaces, if iwd is done After=systemd-udev-settle.service
> with UseDefaultInterface=true, no double-renaming should happen for the
> interfaces directly detected during boot?

systemd-udev-settle.service is a hack and should not be used.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20210222/8ccf2f52/attachment.sig>