Balena Fin Wireless is named mlan0 (not wlan0)

network

#1

As described here: https://bucknall.codes/blog/2018/review-resin-fin/

We had built some scripts where the interface name was hardcoded and it no longer works. Not a huge issue but I was wondering if this was intentional or will change in the future?

Could someone provide instructions on how I could rename this interface in our Docker Template?

cc: @bucknall :slight_smile:


#4

Hi @rcullen!

If you open a terminal session into your Fin (Host OS) and run the command:

$ nmcli d

You should see which devices that your network manager is controlling! If you could share an image of the output of this command, we should be able to work out if the network manager has found the wlan device :slightly_smiling_face:


#7

hey @bucknall thanks for the quick response!

Here is the device, mlan0 what we’d like to rename to wlan0 if possible.

root@xxxxxxxx:/usr/src/app# nmcli d
DEVICE           TYPE      STATE        CONNECTION
mlan0            wifi      connected    resin-wifi-01
resin-dns        bridge    connected    resin-dns
supervisor0      bridge    connected    supervisor0
eth0             ethernet  unavailable  --
balena0          bridge    unmanaged    --
br-d5361ab53eec  bridge    unmanaged    --
lo               loopback  unmanaged    --
resin-vpn        tun       unmanaged    --

#8

Ah ok! I don’t know if there is an easy way to do this, unfortunately… I think this is being set from the kernel module. I’ve been chatting with the Resin team and they’re looking into a solution for this, i.e. possibly an alternative driver with wlan0 set instead of mlan0; I’ll let you know as soon as I do!


#9

@bucknall ok cool!

It’s not urgent, I think I will work around it my end so that my scripts will work if I later have additional interfaces.

If anyone from Resin is reading this it’s not important/urgent. Just a NTH. Thanks guys!