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

[Marco d'Itri]

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.

> 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.

> For an example why this matters, think firewall rules: while I might
> legitimately want to SSH into my laptop over Ethernet or WiFi (e.g. from
> my phone when I'm in the other room), there's no reason I would want
> arbitrary people on the Internet (WiMAX) to SSH in.  Of course, I have
> appropriate security measures in place, but I'd still want to firewall
> incoming WiMAX connections, and using an appropriate naming scheme makes
> that possible.
You can still manually set any persistent name you like.

-- 
ciao,
Marco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 648 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150809/6e4a02aa/attachment-0002.sig>