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
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
Am 22.02.21 um 14:38 schrieb Michael Biebl:
So you basically have an unfixable race due to the design decisions of
iwd. This is why you can do any udev based interface renaming when you
^
can't
OpenPGP_signature
Description: OpenPGP digital
Am 18.02.21 um 21:20 schrieb Michael Biebl:
Am 18.02.2021 um 21:03 schrieb Yuri D'Elia:
On Thu, Feb 18 2021, Michael Biebl wrote:
There is afaics.
udev announces devices only after it has fully processed all udev rules.
Asking here since it's on topic and you might be more familiar with it
Am 18.02.2021 um 21:03 schrieb Yuri D'Elia:
On Thu, Feb 18 2021, Michael Biebl wrote:
There is afaics.
udev announces devices only after it has fully processed all udev rules.
Asking here since it's on topic and you might be more familiar with it
than I am: as these devices also emitted as an
On Sun, Feb 14 2021, Michael Biebl wrote:
>> 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
Am 13.02.2021 um 19:02 schrieb 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
On Sat, Feb 13 2021, Michael Biebl wrote:
>> If I want to keep exiting interface names I'd rather have to do this
>> configuration explicitly.
>
> By masking 80-iwd.link, both udev and iwd race against each other.
> Sometimes udev is fast enough to rename the interface, sometimes iwd is
> quick
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
Hello Michael, Yuri,
On Sat, Feb 13, 2021 at 06:45:11PM +0100, Yuri D'Elia wrote:
> On Sat, Feb 13 2021, Michael Biebl wrote:
> >> If I want to keep exiting interface names I'd rather have to do this
> >> configuration explicitly.
> >
> > By masking 80-iwd.link, both udev and iwd race against
On Sat, 13 Feb 2021 15:28:24 +0100 Yuri D'Elia
wrote:
> Package: udev
> Version: 247.3-1
> Severity: normal
>
> I recently switched to a different laptop which is marginally faster.
> Using this laptop, the wireless interface name changes from wlan0 to
> wlo1 seemingly randomly across reboots,
11 matches
Mail list logo
