1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

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

    From Roy J. Tellason, Sr.@21:1/5 to All on Wed Jun 12 20:50:01 2024
    On Wednesday 12 June 2024 06:54:54 am Richard wrote:
    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.

    --
    Member of the toughest, meanest, deadliest, most unrelenting -- and
    ablest -- form of life in this section of space, �a critter that can
    be killed but can't be tamed. �--Robert A. Heinlein, "The Puppet Masters"
    -
    Information is more dangerous than cannon to a society ruled by lies. --James M Dakin

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From [email protected]@21:1/5 to Sr. on Wed Jun 12 21:10:02 2024
    On Wed, Jun 12, 2024 at 02:30:40PM -0400, Roy J. Tellason, Sr. wrote:
    On Wednesday 12 June 2024 06:54:54 am Richard wrote:
    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
    --
    t

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZmnwmAAKCRAFyCz1etHa RosZAKCBjcLCn1szlfQ7HhsZyJbyHvCxIACeLYKbbOuy2+YFEikEabKL/P/z01A=
    =BZdj
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From [email protected]@21:1/5 to Richard on Wed Jun 12 21:50:01 2024
    Richard <[email protected]> wrote:
    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 < [email protected]>:

    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/[email protected]/T/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Greg Wooledge@21:1/5 to [email protected] on Wed Jun 12 21:20:01 2024
    On Wed, Jun 12, 2024 at 09:01:44PM +0200, [email protected] wrote:
    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"

    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.

    https://wiki.debian.org/NetworkInterfaceNames

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From [email protected]@21:1/5 to Greg Wooledge on Thu Jun 13 06:40:01 2024
    On Wed, Jun 12, 2024 at 03:16:41PM -0400, Greg Wooledge wrote:
    On Wed, Jun 12, 2024 at 09:01:44PM +0200, [email protected] wrote:

    [...]

    Mine loks like this:

    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.

    Absolutely. I did, and I decided that in my case, this is the better
    choice...

    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.

    ...but it's not always, as you say.

    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.

    I think PCI is not the worst offender. The worst is if you have a bunch
    of adapters hanging off an USB tree. Then, as they say, God does play
    dice :-)

    Back Then (TM) (I think it was a Debian 3.x aka Sarge), a bunch of
    us cobbled a "router thingy" together on some off-the-shelf hardware.
    It had four Ethernets hanging off whatever PC bus was fashionable
    back then (too lazy to look it up).

    Not many of those were sold, luckily :-)

    One was for "the bad Internet", the other three for "the inside".
    Our big fear was that, after a BIOS upgrade the interfaces would
    come up in a mangled order. That would have been a good application
    of this scheme (provided it works at all: I'm somewhat sceptic.
    Hardware and firmware are known to do... things).

    We ended up going by the card's MAC addresses, at the price of
    having a set up step on assembly. But then, if you change one
    Ethernet card...

    Alas, you can't do it right.

    For my laptop, I very much prefer to say "sudo ifup eth0" than to
    say "sudo ifup en0ps&&@*#!☠" thankyouverymuch :)

    Cheers
    --
    t

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZmp13AAKCRAFyCz1etHa RlJ0AJ9S/60xApOftKR3EldYJszFgUd1KgCePPHIgJ+aH7CivITCBkjgrFP0rJA=
    =+8dm
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From [email protected]@21:1/5 to [email protected] on Thu Jun 13 06:40:01 2024
    On Thu, Jun 13, 2024 at 06:30:27AM +0200, [email protected] wrote:

    [following up on myself, bad style, I know]

    For my laptop, I very much prefer to say "sudo ifup eth0" than to
    say "sudo ifup en0ps&&@*#!☠" thankyouverymuch :)

    and of course, if you are using a desktop environment and NetworkManager
    or systemd-networkd, it's probably better to go with the flow and let
    them do.

    Cheers
    --
    t

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZmp2wwAKCRAFyCz1etHa RiywAJ45c03fkvibg7CjxzdXNK0xZ36BtwCeMJxnNBF6FWZfALTbw2/AFSB5Tjo=
    =eOpb
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)