Am Mi., 5. Jan. 2022 um 13:50 Uhr schrieb Mantas Mikulėnas :
> It does, yes, but note this part:
>
> Jan 03 11:30:14 nasl002b.example.com kernel: igb :02:00.2 eth4: renamed
> from eth2
> Jan 03 11:30:14 nasl002b.example.com kernel: igb :02:00.3 eth5: renamed
> from eth3
>
> Here the
On 2022-01-05 13:50:29, Mantas Mikulėnas wrote:
On Wed, Jan 5, 2022 at 9:46 AM Harald Dunkel
AFAICS the kernel of today still assigns the "legacy" interface names,
which are renamed by udev later. I would suggest to improve conflict
It does, yes, but note this part:
Jan 03 11:30:14
On 2022-01-05 11:17:20, Martin Wilck wrote:
This is default behavior. To disable it, you need to use
"net.ifnames=0". If you see the same value multiple times for either
"acpi_index" or "index", it'd be a firmware problem. I suppose it can
happen that one device has acpi_index==1 and another
On Wed, Jan 5, 2022 at 9:46 AM Harald Dunkel
wrote:
> On 2022-01-04 16:14:16, Andrei Borzenkov wrote:
> >
> > You have two interfaces which export the same onboard interface index.
> > There is not much udev can do here; the only option is to disable
> > onboard interface name policy. The
On Wed, 2022-01-05 at 08:39 +0100, Harald Dunkel wrote:
> On 2022-01-04 16:14:16, Andrei Borzenkov wrote:
> >
> > You have two interfaces which export the same onboard interface
> > index.
> > There is not much udev can do here; the only option is to disable
> > onboard interface name policy. The
