Please help me identify package so I can report an important bug

[Peter Goodall]

Hello,

This bug, or a close relative, has already been reported in
https://github.com/raspberrypi/bookworm-feedback/issues/239
as 'Predictable network names broken for ASIX USB ethernet in kernel 6.6.20'

I added a comment reporting my experience in Proxmox here:
https://github.com/raspberrypi/bookworm-feedback/issues/239#issuecomment-2162166863

Because it happens in proxmox and rpi I assume its Debian or higher. I have
not reported a Debian bug before...

Thanks,
--Peter G

[Richard]

Question is, does it make that much sense to report it to Debian directly?
Are you encountering this issue on Debian itself or
Armbian/Raspbian/whatever? You reported this to the Raspberry Pi GitHub, so
I'd expect them to take this up with the upstream devs themselves, so by
the time Trixie is being released, it may already be included.

But besides that, what you describe in the first link sounds to me not like
a bug, but as a well thought-through decision. Network adapter names like
eth0 have been dropped with Debian 11 (I think, maybe even 10). So don't
get your hopes up too high to ever see this coming back. But also, just
searching the web for this topic, you should have come across this
answering your questions: https://wiki.debian.org/NetworkInterfaceNames

Richard

Am Mi., 12. Juni 2024 um 12:43 Uhr schrieb Peter Goodall <

Post by Peter Goodall
Hello,
This bug, or a close relative, has already been reported in
https://github.com/raspberrypi/bookworm-feedback/issues/239
as 'Predictable network names broken for ASIX USB ethernet in kernel 6.6.20'
https://github.com/raspberrypi/bookworm-feedback/issues/239#issuecomment-2162166863
Because it happens in proxmox and rpi I assume its Debian or higher. I
have not reported a Debian bug before...
Thanks,
--Peter G

[Jeffrey Walton]

Question is, does it make that much sense to report it to Debian directly? Are you encountering this issue on Debian itself or Armbian/Raspbian/whatever? You reported this to the Raspberry Pi GitHub, so I'd expect them to take this up with the upstream devs themselves, so by the time Trixie is being released, it may already be included.
But besides that, what you describe in the first link sounds to me not like a bug, but as a well thought-through decision. Network adapter names like eth0 have been dropped with Debian 11 (I think, maybe even 10). So don't get your hopes up too high to ever see this coming back. But also, just searching the web for this topic, you should have come across this answering your questions: https://wiki.debian.org/NetworkInterfaceNames

The random MAC address discussed in the bug report (with mention of
Network Manager) could be
<https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/>.

Jeff

[Richard]

Good catch. With the title of this thread and not seeing any proper
description of what's actually wrong on GitHub, I figured the change of the
adapter name was meant. Yes, with MAC randomization, that's what you'll
get. But it's nothing Debian defaults to. So question is, can this be
disabled on Proxmox? But with this hint, it should be easy enough to figure
out if this can be deactivated on the affected systems, and if not the bug
reports must be against these issues, as Debian itself doesn't do such
things. If it is an issue with Debian preventing the disablement, the devs
need to talk to each other.

Richard

Am Mi., 12. Juni 2024 um 17:10 Uhr schrieb Jeffrey Walton <

Post by Jeffrey Walton
The random MAC address discussed in the bug report (with mention of
Network Manager) could be
<
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/

.

Jeff

[d***@howorth.org.uk]

Post by Richard
Good catch. With the title of this thread and not seeing any proper
description of what's actually wrong on GitHub, I figured the change
of the adapter name was meant. Yes, with MAC randomization, that's
what you'll get. But it's nothing Debian defaults to. So question is,
can this be disabled on Proxmox? But with this hint, it should be
easy enough to figure out if this can be deactivated on the affected
systems, and if not the bug reports must be against these issues, as
Debian itself doesn't do such things. If it is an issue with Debian
preventing the disablement, the devs need to talk to each other.
Richard
Am Mi., 12. Juni 2024 um 17:10 Uhr schrieb Jeffrey Walton <

Post by Jeffrey Walton
The random MAC address discussed in the bug report (with mention of
Network Manager) could be
<
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/

.

Jeff

I think before anybody else suggests anything, they should read
https://lore.kernel.org/netdev/***@kernel.org/T/

[Roy J. Tellason, Sr.]

Post by Richard
But also, just
searching the web for this topic, you should have come across this
answering your questions: https://wiki.debian.org/NetworkInterfaceNames

Wow. Just wow...

That sort of thing just drives me crazy! :-)

I can see sticking with older versions of some things.

[t***@tuxteam.de]

Post by Roy J. Tellason, Sr.

Post by Richard
But also, just
searching the web for this topic, you should have come across this
answering your questions: https://wiki.debian.org/NetworkInterfaceNames

Wow. Just wow...
That sort of thing just drives me crazy! :-)
I can see sticking with older versions of some things.

No need. You can have your traditional names (I do). Just add
"net.ifnames=0" (if necessry separated by a space, should
other stuff be already there) to your GRUB_CMDLINE_LINUX_DEFAULT
in your /etc/default/grub, then ru update-grub.

Mine loks like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0"

Cheers

[Greg Wooledge]

Post by t***@tuxteam.de
No need. You can have your traditional names (I do). Just add
"net.ifnames=0" (if necessry separated by a space, should
other stuff be already there) to your GRUB_CMDLINE_LINUX_DEFAULT
in your /etc/default/grub, then ru update-grub.
GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0"

People who are thinking of doing this should take a moment to consider
whether it will be better or worse than the default.

For a machine that has exactly one ethernet interface, this is a vast
improvement over the default. Your interface will always be named
"eth0" no matter what crazy things happen on the PCI bus.

For a machine with multiple interfaces, however, the original problem
that "predictable interface names" were supposed to solve is still an
issue. The kernel may not assign the names in the same order every
time you boot. In that situation, "net.ifnames=0" is not likely to
be an improvement. You'd be better off using systemd.link(5) files to
customize your interface names according to your own specific needs.

Post by t***@tuxteam.de

Post by Richard
https://wiki.debian.org/NetworkInterfaceNames