Bug#794969: udev: change in network device naming scheme unnecessarily and incorrectly renames WiMAX devices

[brian m. carlson]

On 2019-12-02 at 17:04:29, Michael Biebl wrote:
> Control: tags -1 + moreinfo
> 
> 
> Hi
> 
> On Mon, 10 Aug 2015 23:25:36 +0000 "brian m. carlson"
> <sandals at crustytoothpaste.net> wrote:
> > On Sun, Aug 09, 2015 at 05:54:29PM +0200, Marco d'Itri wrote:
> > > On Aug 08, "brian m. carlson" <sandals at crustytoothpaste.net> wrote:
> > > 
> > > > Previously, my WiMAX device was named something like wmx0.  Now, it
> > > > appears it's been renamed to enx<MAC Address>.  First of all, the name
> > > > has changed from what it used to be, and now I have to check that it's
> > > > not broken anything.  There wasn't supposed to be a naming change for
> > > > people with the persistent-net rules in place.
> > > Indeed: what was the content of your 70-persistent-net.rules file?
> > > I suspect that persistent naming just never worked for you for this
> > > interface.
> > 
> > The interface is clearly missing:
> > 
> >   # PCI device 0x8086:/sys/devices/pci0000:00/0000:00:19.0 (e1000e)
> >   SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f0:de:f1:b8:36:fd", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
> >   
> >   # PCI device 0x8086:/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0 (iwlwifi)
> >   SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="64:80:99:4f:73:a0", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
> > 
> > I suppose the idea was to skip USB devices, thinking that they were all
> > removable, but I can't be certain without seeing the generator, which
> > has been removed.
> > 
> > > > Secondly, this is not an Ethernet device, so en is not correct (it
> > > > should be ww).  The device is on the USB bus (using the driver
> > > > i2400m-usb).
> > > I do not think that such a distinction is relevant here.
> > 
> > If you're going to autogenerate the name, please autogenerate it such
> > that it's consistent with the naming scheme.  The comment in
> > udev-builtin-net_id.c indicates that ww is appropriate here.  People
> > should be able to predict interface names, such that configuration can
> > be autogenerated (e.g. for puppet).  Naming some WWAN devices as ww but
> > others as en is silly.
> 
> 
> Is this issue still valid?
> I do have an (internal) wimax device which is named wwx02803XXXXX, i.e.
> has the ww prefix as one would expect.
> 
> If it's still a problem, please attach the output of
> udevadm info /sys/class/net/$(iface)

I'm unsure.  The issue is now four years old and I'm using a different
laptop without a WiMAX card.  If you're sure that it's been fixed, I'm
fine with you closing it.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 868 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20191203/f8ba1ea7/attachment.sig>