On 2022-01-06 13:23:37, Michael Biebl wrote:
Am Do., 6. Jan. 2022 um 10:00 Uhr schrieb Mantas Mikulėnas :
Grep your entire /etc for those interface names (starting with /etc/udev), find
out where they're defined, and remove them
Please also make sure to rebuild your initramfs after doing
Am Do., 6. Jan. 2022 um 10:00 Uhr schrieb Mantas Mikulėnas :
> Grep your entire /etc for those interface names (starting with /etc/udev),
> find out where they're defined, and remove them
Please also make sure to rebuild your initramfs after doing that.
Files from /etc/udev are usually embedded
On Thu, Jan 6, 2022 at 10:42 AM Harald Dunkel
wrote:
> On 2022-01-05 21:48:11, Michael Biebl wrote:
> > Am Mi., 5. Jan. 2022 um 13:50 Uhr schrieb Mantas Mikulėnas <
> graw...@gmail.com>:
> >> It does, yes, but note this part:
> >>
> >> Jan 03 11:30:14 nasl002b.example.com kernel: igb
On 2022-01-05 21:48:11, Michael Biebl wrote:
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:
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
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 attributes that are used by udev
are "acpi_index" and "index". Check
On Tue, Jan 4, 2022 at 4:53 PM Harald Dunkel wrote:
>
> Hi folks,
>
> after the upgrade from Buster to Bullseye (including the migration from
> sysv init to systemd) the network interface names were messed up on
> several hosts. Apparently udev stumbles over a naming conflict:
>
> # journalctl -b
Hi folks,
after the upgrade from Buster to Bullseye (including the migration from
sysv init to systemd) the network interface names were messed up on
several hosts. Apparently udev stumbles over a naming conflict:
# journalctl -b | egrep -i e1000e\|igb\|rename\|eth\enp\|eno
Jan 03 11:30:14
12 matches
Mail list logo