Bug#982688: wireless interface name unstable across reboots

[Yuri D'Elia]

On Sat, Feb 13 2021, Andreas Henriksson wrote:
>> Is it possible to synthesize a target for network interface names, to be
>> reached when all network interface names have settled somehow?
>
> As I see it the problem is that you currently have 2 options, but you
> configured things to be in a broken middle state.
>
> Either you don't care about interface names and you disable the udev
> rules for wireless interfaces (iwd default config),
> or you say that naming is more important than speed to you so you mask
> the configuration shipped by iwd and then make iwd wait for udev rules
> to be applied.

Sure. But then again it's exactly the question I have above: what do I
wait "on" in order to ensure interface names have settled?

> I've not seen any other practically workable options available right now
> without having to do fundamental changes to existing policies in other
> software - not udev or iwd (eg. linux, et.al.)

I'd like, ideally, to keep stable interface names. I'm not sure if this
is intended, but so far after masking 80-iwd and removing "keep" from
the NamePolicy it seems that udev is always able to rename the interface
across reboots.

It might entirely be because iwd started to operate on the original
device name, but didn't have time to bring it up before the rename
happens I guess.