sudo tee /etc/udev/rules.d/80-net-setup-link.rules <<EOF
SUBSYSTEM!="net", GOTO="net_setup_link_end"
IMPORT{builtin}="path_id"
ACTION!="add", GOTO="net_setup_link_end"
# IMPORT{builtin}="net_setup_link"
NAME=="", ENV{ID_NET_NAME}!="", NAME="wlan0"
LABEL="net_setup_link_end"
EOF
I use a rule like this to insure the ethernet interface comes up as eth0 on Pi3's.
]]>... Devuan on both Pi4b and Pi400, in aarch64 mode.
... WIFI interface is named WLAN0 on the Pi4b ...
... named WLAN1 on the Pi400 ...
Any clues?
Can't imagine why.
But check this and see if there's something there: https://wiki.debian.org/NetworkInterfaceNames
eg: the /etc/udev/rules.d/70-persistent-net.rules file in each one of the installations and compare them.
Best,
A.
]]>I use Devuan on both Pi4b and Pi400, in aarch64 mode.
In both cases, I manually load the bcrmfmac module when it's needed.
The problem is that the WIFI interface is named WLAN0 on the Pi4b but it's named WLAN1 on the Pi400, and that breaks some of my scripts.
So, what could be at play here? Any clues?
Thanks!
]]>