Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #245466
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? |
| Date | 2022-02-16 15:50 +0100 |
| Message-ID | <DRtMZ-2dx0-3@gated-at.bofh.it> (permalink) |
| References | <DRpgm-2aFX-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi. On Wed, Feb 16, 2022 at 03:55:21AM -0600, Flacusbigotis wrote: > Back in Debian Buster, I learned that the "predictive" naming of this USB > ethernet interface would be governed by "73-usb-net-by-mac.rules" and so I > had it configured accordingly with a config file in > /etc/network/interfaces.d/... Namely that the device name would basically > be its MAC. It's still true in Bullseye, but the implementation has changed somewhat. Instead of /lib/udev/rules.d/73-usb-net-by-mac.rules now systemd uses /lib/systemd/network/73-usb-net-by-mac.link. > Well, I just upgraded to Bullseye, and I can't bring up the darn > interface. I have tried fiddling around with the device name in my config > file in /etc/network/interfaces.d/ directory, but it just won't come up. > The Networking.service also fails during bootup. A straightforward approach would be to learn the actual name of the device via "ip a"/"ifconfig -a", and then using that name in /e/n/i. > Anyone know how the heck this is supposed to work in Bullseye? systemd.link(5), systemd.net-naming-scheme(7). The keyword you need is NamePolicy=mac. > BTW, the device shows up as disabled in lshw (I obfuscated the MAC in the > output): > > *-network DISABLED That could mean anything. Please show the output of "ip a". Reco
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Flacusbigotis <flacusbigotis@gmail.com> - 2022-02-16 11:00 +0100
Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Reco <recoverym4n@enotuniq.net> - 2022-02-16 15:50 +0100
Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Greg Wooledge <greg@wooledge.org> - 2022-02-16 16:00 +0100
Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Flacusbigotis <flacusbigotis@gmail.com> - 2022-02-17 07:40 +0100
Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Reco <recoverym4n@enotuniq.net> - 2022-02-17 08:10 +0100
Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Flacusbigotis <flacusbigotis@gmail.com> - 2022-02-22 03:00 +0100
Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Reco <recoverym4n@enotuniq.net> - 2022-02-22 12:20 +0100
Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Nicholas Geovanis <nickgeovanis@gmail.com> - 2022-02-22 18:00 +0100
Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Reco <recoverym4n@enotuniq.net> - 2022-02-22 19:00 +0100
Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Flacusbigotis <flacusbigotis@gmail.com> - 2022-02-23 05:40 +0100
Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Tixy <tixy@yxit.co.uk> - 2022-02-23 10:20 +0100
Re: 73-usb-net-by-mac.rules is no longer used in Bullseye for USB ethernet devices? Flacusbigotis <flacusbigotis@gmail.com> - 2022-02-23 18:50 +0100
csiph-web