Following this thread (USB to Ethernet adapter works with Reach M+ but not with M2) we tried hooking up a TP-Link adapter to our M2 modules.
The reason is we want to connect the USB0 port to a wired device and use the M2 as access point via its wifi connection.
This works perfectly for the No1 M2 (with 2.22 firmware). The device gets an IP address on USB0 (192.168.6.40) and we can ping devices on the .6.x network while connected to the M2 wifi (the 192.168.42.1 access point). However for the other M2 this does not work.
We get the following behavior:
M2 no1: Firmware 2.22 gets an IP address on USB0 from our DHCP server
M2 no2: Firmware 2.24 does not get an address.
A SSH session tells me:
nmcli device show:
GENERAL.STATE: 20 (unavailable)
Has there a change in the firmware causing this? Any help greatly appreciated