Page 1 of 1

Stretch Networking

Posted: Fri Aug 18, 2017 6:55 am
by Milliways
I just installed Stretch, and performed a clean install.

As expected there also appears to be a (partial?) change to predictable network interface names https://www.debian.org/releases/stretch ... face-names

The Ethernet name is now based on MAC, but continues to use wlan0 for the Wireless Interface.

There seems to be no mention of the change in the release notes, and in particular, why Wireless Interface wlan0 remains.

Is there any reason for the partial change?

Re: Stretch Networking

Posted: Fri Aug 18, 2017 7:20 am
by RaTTuS

Re: Stretch Networking

Posted: Fri Aug 18, 2017 8:24 am
by Milliways
I am aware of this, but I was looking for some Raspbian specific link, and specifically the reason why NOT wlan0.

Re: Stretch Networking

Posted: Fri Aug 18, 2017 11:49 am
by jamesh
The WiFi chip is connected over sdio, not usb, this mac address naming is for usb attached devices.

Re: Stretch Networking

Posted: Fri Aug 18, 2017 7:44 pm
by elkberry
Using the officially posted "fix" for returning to the "unstable", yet stable naming scheme by setting the appropriate symlink caused my wireless LAN interface to completely disappear. Well done.

Re: Stretch Networking

Posted: Sat Aug 19, 2017 8:03 am
by jamesh
No need for thanks, that needs to go upstream to the people in Linux land who made the change. Nothing to do with RPF.

Note also, the previous naming scheme was not stable. With two usb adaptors you could not guarantee which becomes eth0. That is why the change was made. Whether it's a good change, dunno.

Re: Stretch Networking

Posted: Sat Aug 19, 2017 10:02 am
by runboy93
https://raspberrypi.stackexchange.com/q ... 7921#37921

Raspberry Pi foundation can do nothing for this problem, we need wait longer for fix :/

Re: Stretch Networking

Posted: Sat Aug 19, 2017 11:12 am
by Martin Frezman
runboy93 wrote:
Sat Aug 19, 2017 10:02 am
https://raspberrypi.stackexchange.com/q ... 7921#37921

Raspberry Pi foundation can do nothing for this problem, we need wait longer for fix :/
The Raspbian maintainers *could* change (fix) this, by any of the 3 documented methods (*), but it is not clear that they would be ideologically compatible with doing so. Like systemd, it seems this trend is, like it or not, the future. As a mentor told me back in the 80s, the key to survival in the world of Personal Computing is "Don't buck trends".


(*) I think (emphasis on that word) that the most straightforward method would be the "cmdline.txt" method, since I would assume that that file is not controlled by "upstream", as it is RPi-specific.

Re: Stretch Networking

Posted: Sat Aug 19, 2017 11:35 am
by epoch1970
jamesh wrote:
Sat Aug 19, 2017 8:03 am
Note also, the previous naming scheme was not stable. With two usb adaptors you could not guarantee which becomes eth0. That is why the change was made. Whether it's a good change, dunno.
I thought in this case you would use a udev rule and fix names according to MACs.
I'm pretty sure I did that and it was working. Was I lucky?