# Station Mode Issue with Voxl Suite 1.6.3

Source: https://forum.modalai.com/topic/5099/station-mode-issue-with-voxl-suite-1-6-3
Category: General Questions (https://forum.modalai.com/category/2/general-questions)
Posted: 2026-03-12 06:39:51 UTC by Matt69
Replies: 22 · Views: 2186

## Matt69 · 2026-03-12 06:39:51 UTC

Hello Modal AI team,

I just flashed my Voxl2 with the newest SDK 1.6.3. The issue is I cannot seem to get station mode working with voxl-wifi. Is this a common bug or am I missing something here? Here is my system info from the abd shell "intro" for reference. 

![44e847a2-a37c-4b77-8c21-9ed04fa0c222-image.png](https://forum.modalai.com/assets/uploads/files/1773297565877-44e847a2-a37c-4b77-8c21-9ed04fa0c222-image.png) 

Thanks!

## Reply by Matt69 · 2026-03-12 17:14:24 UTC

@Matt69 For further clarification, my understanding is that a 169.XXX.XXX.XXX IP address indicates off nominal wifi performance. Please advise.

Thanks!

## Reply by Alex Kushleyev (ModalAI staff) · 2026-03-18 04:52:19 UTC (in reply to Matt69)

Hi @Matt69 ,

Yes, the shown ip address is a self-assigned address which happens if there is no ip address assigned by a DHCP server.

What wifi module are you using?

Does output of `iwconfig wlan0` show that you are connected to your Access Point?

Alex

## Reply by fhaltmayer · 2026-03-18 14:45:27 UTC (in reply to Alex Kushleyev)

I'm also facing this after updating. Worked on an older version but it is now defaulting to the link local. One thing I noticed is that it doesn't go through the connection process (finding the network, trying password, etc) when using voxl-wifi, just skips all of it:

Configuring station mode...
Detected WiFi interface: wlan0
NetworkManager not installed, using legacy wpa_supplicant/hostapd
stopping softap mode
Enabling station mode on wlan0 (legacy)...
creating wpa_supplicant configuration for station mode
Station mode enabled on wlan0
Station mode configured!

This is using the MCBL-00022 kit on the voxl2.

Downgrading to 1.6.2 and the wifi works but seems a bit bugged because it cant find it at first even though it connects successfully :

Detected WiFi interface: wlan0
Disabling all WiFi modes...
Detected WiFi interface: wlan0
Scanning for network 'xxx'...
Scan succeeded, looking for network 'xxx'
Could not find network 'xxx' in scan results - proceeding anyway
Enabling station mode on wlan0...
creating wpa_supplicant configuration for station mode
Station mode enabled on wlan0
Station mode configured!

## Reply by Alex Kushleyev (ModalAI staff) · 2026-03-18 22:07:28 UTC (in reply to fhaltmayer)

@fhaltmayer , which wifi usb adapter are you using?

## Reply by fhaltmayer · 2026-03-19 13:51:37 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev The Alfa Network AWU2036

## Reply by Alex Kushleyev (ModalAI staff) · 2026-03-31 03:32:36 UTC (in reply to fhaltmayer)

@fhaltmayer ,

SDK 1.6.3 added support for usb-eth0 (ethernet over usb). That interface should be using subnet 192.168.7.x. If your wifi subnet is the same, that could cause issues. Can you please check to make sure your wifi subnet is different?

Alex

## Reply by Alex Kushleyev (ModalAI staff) · 2026-04-02 21:40:25 UTC (in reply to Alex Kushleyev)

I have just tested this on voxl2 using SDK 1.6.3 and it seems to be working. The prints were updated, but what you see is normal (i saw the same messages). Did you check `dmesg` for any errors from wifi dongle? I used the following wifi adapter, which is unfortunately EOL (with our M0141 expansion board) :

![30d3fe55-c5dd-49a9-8d65-3b2baadd3179-image.png](https://forum.modalai.com/assets/uploads/files/1775165943381-30d3fe55-c5dd-49a9-8d65-3b2baadd3179-image.png) 

```bash
────────────────────────────────────────────────────────────────────────────────
system-image: 1.8.06-M0054-14.1a-perf
kernel:       #1 SMP PREEMPT Wed Oct 22 04:13:18 UTC 2025 4.19.125
────────────────────────────────────────────────────────────────────────────────
hw platform:  M0054
mach.var:     1.0.1
SKU:          MCCA-M0054-C8
────────────────────────────────────────────────────────────────────────────────
voxl-suite:   1.6.3
────────────────────────────────────────────────────────────────────────────────
no current network connection
────────────────────────────────────────────────────────────────────────────────

voxl2:/$ voxl-wifi station xxxxxx yyyyyy
Detected WiFi interface: wlan0
NetworkManager not installed, using legacy wpa_supplicant/hostapd
stopping softap mode
Enabling station mode on wlan0 (legacy)...
creating wpa_supplicant configuration for station mode
Station mode enabled on wlan0
Station mode configured!

voxl2:/$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=118 time=11.806 ms
```

## Reply by SKA · 2026-04-03 16:24:20 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev Hi!

I'm facing the same issue using station mode on sdk v1.6.3.
I've tried using the ALFA AWU2036 as well as the TP-LINK AC600.
Changing back to sdk 1.6.0, it works as expected.

```
voxl2-mini (M0104):/$ voxl-my-ip
169.254.233.208 (wlan0)
voxl2-mini (M0104):/$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
92 bytes from 169.254.233.208: Destination Host Unreachable
92 bytes from 169.254.233.208: Destination Host Unreachable
92 bytes from 169.254.233.208: Destination Host Unreachable
92 bytes from 169.254.233.208: Destination Host Unreachable
92 bytes from 169.254.233.208: Destination Host Unreachable
^C92 bytes from 169.254.233.208: Destination Host Unreachable
--- 8.8.8.8 ping statistics ---
7 packets transmitted, 0 packets received, 100% packet loss
voxl2-mini (M0104):/$ cat /data/misc/wifi/wpa_supplicant.conf
# Only WPA-PSK is used. Any valid cipher combination is accepted.
ctrl_interface=/var/run/wpa_supplicant
update_config=1

network={
#Open
#        ssid="example open network"
#        key_mgmt=NONE
#WPA-PSK
        ssid="xxxxxxx"
        #proto=WPA
        key_mgmt=WPA-PSK
        pairwise=TKIP CCMP
        group=TKIP CCMP
        psk="yyyyyyy"
#WEP
#       ssid="example wep network"
#       key_mgmt=NONE
#       wep_key0="abcde"
#       wep_key1=0102030405
#       wep_tx_keyidx=0
}
wowlan_triggers=magic_pkt
voxl2-mini (M0104):/$ cd data/misc/wifi/
voxl2-mini (M0104):/data/misc/wifi$ ls
hostapd.conf  station_band  station_interface  station_ssid  wlan_mode  wpa_supplicant.conf
voxl2-mini (M0104):/data/misc/wifi$ cat station_band
2ghz
```

## Reply by Alex Kushleyev (ModalAI staff) · 2026-04-03 16:29:40 UTC (in reply to SKA)

@SKA , I don't have a file "station_band", also 2ghz seems incorrect (maybe it should be 2.4ghz? not sure). Try to rename / remove that file?

what does `iwconfig wlan0` output? what about dmesg? anything useful?

Alex

## Reply by SKA · 2026-04-03 17:58:30 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev I didn't add the station_band file, and this is a freshly flashed voxl. Removing/changing it to 2.4ghz didn't help unfortunately.

```
voxl2-mini (M0104):/$ iwconfig wlan0
wlan0     unassociated  ESSID:""  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated
          Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/100  Signal level=0 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
```

## Reply by Alex Kushleyev (ModalAI staff) · 2026-04-03 18:13:50 UTC (in reply to SKA)

@SKA , can you please try to power down the wifi device and power it back up (using the commands below) and check the output of dmesg. 

```
#turn off USB VBUS
voxl-gpio write 157 0

#turn on USB VBUS
voxl-gpio write 157 1
```

my dmesg output:
```
[   24.123592] usb 1-1: USB disconnect, device number 2
[   24.152384] RTW: rtw_ndev_uninit(wlan0) if1
[   24.172973] RTW: rtw_dev_unload: driver not in IPS
[   33.464284] usb 1-1: new high-speed USB device number 3 using xhci-hcd
[   33.602465] usb 1-1: New USB device found, idVendor=0bda, idProduct=c820, bcdDevice= 2.00
[   33.602487] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   33.602502] usb 1-1: Product: 802.11ac NIC
[   33.602517] usb 1-1: Manufacturer: Realtek
[   33.602531] usb 1-1: SerialNumber: 123456
[   33.614447] RTW: [HALMAC]55772M
               HALMAC_MAJOR_VER = 1
               HALMAC_PROTOTYPE_VER = 6
               HALMAC_MINOR_VER = 6
               HALMAC_PATCH_VER = 22
[   33.760178] vdd_tof: disabling
[   33.760182] vdd_hap_boost: disabling
[   33.835010] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
[   33.835034] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
[   33.835055] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
[   33.835075] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
[   33.835095] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
[   33.835115] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
[   33.951477] RTW: HW EFUSE
[   33.951489] RTW: 0x000: 29 81 00 BC  09 00 21 00  6E 04 A4 34  10 00 30 0B  
[   33.951530] RTW: 0x010: 26 26 26 26  26 26 27 27  27 27 27 13  FF FF FF FF  
[   33.951570] RTW: 0x020: FF FF 2D 2D  2D 2D 2D 2D  2D 2D 2D 2D  2D 2D 2D 2D  
[   33.951632] RTW: 0x030: 13 FF FF FF  FF FF E0 FF  FF FF 28 28  28 28 28 28  
[   33.951671] RTW: 0x040: 28 28 28 28  28 02 FF FF  FF FF FF FF  FF FF FF FF  
[   33.951710] RTW: 0x050: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.951749] RTW: 0x060: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.951788] RTW: 0x070: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.951827] RTW: 0x080: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.951866] RTW: 0x090: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.951904] RTW: 0x0A0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.951943] RTW: 0x0B0: FF FF FF FF  FF FF FF FF  7F 1A 1B 00  FF FF FF FF  
[   33.951982] RTW: 0x0C0: FF 22 00 00  00 E6 00 00  00 FF 26 FF  FF FF FF FF  
[   33.952179] RTW: 0x0D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952291] RTW: 0x0E0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952331] RTW: 0x0F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952369] RTW: 0x100: DA 0B 20 C8  C3 46 02 00  C0 CA B3 A4  EC 09 03 52  
[   33.952408] RTW: 0x110: 65 61 6C 74  65 6B 0E 03  38 30 32 2E  31 31 61 63  
[   33.952447] RTW: 0x120: 20 4E 49 43  08 03 31 32  33 34 35 36  FF FF FF FF  
[   33.952486] RTW: 0x130: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952533] RTW: 0x140: FF FF FF FF  00 00 31 0F  FF FF FF FF  FF FF FF FF  
[   33.952602] RTW: 0x150: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952641] RTW: 0x160: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952691] RTW: 0x170: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952730] RTW: 0x180: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952769] RTW: 0x190: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952808] RTW: 0x1A0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952847] RTW: 0x1B0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952885] RTW: 0x1C0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952924] RTW: 0x1D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.952963] RTW: 0x1E0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.953002] RTW: 0x1F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
[   33.953329] RTW: hal_com_config_channel_plan chplan:0x7F
[   34.184253] RTW: [RF_PATH] ver_id.RF_TYPE:RF_1T1R
[   34.184263] RTW: [RF_PATH] HALSPEC's rf_reg_trx_path_bmp:0x11, rf_reg_path_avail_num:1, max_tx_cnt:1
[   34.184269] RTW: [RF_PATH] PG's trx_path_bmp:0x00, max_tx_cnt:0
[   34.184276] RTW: [RF_PATH] Registry's trx_path_bmp:0x00, tx_path_lmt:0, rx_path_lmt:0
[   34.184283] RTW: [RF_PATH] HALDATA's trx_path_bmp:0x11, max_tx_cnt:1
[   34.184288] RTW: [RF_PATH] HALDATA's rf_type:RF_1T1R, NumTotalRFPath:1
[   34.184296] RTW: [TRX_Nss] HALSPEC - tx_nss:1, rx_nss:1
[   34.184301] RTW: [TRX_Nss] Registry - tx_nss:0, rx_nss:0
[   34.184307] RTW: [TRX_Nss] HALDATA - tx_nss:1, rx_nss:1
[   34.184315] RTW: txpath=0x1, rxpath=0x1
[   34.184321] RTW: txpath_1ss:0x1, num:1
[   34.185543] RTW: rtw_regsty_chk_target_tx_power_valid return _FALSE for band:0, path:0, rs:0, t:-1
[   34.188733] RTW: rtw_ndev_init(wlan0) if1 mac_addr=00:c0:ca:b3:a4:ec
[   35.507557] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
```

## Reply by SKA · 2026-04-03 18:21:22 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev After turning it off and on, this was the dmesg output: 
```
[ 1075.483890] usb 1-1: USB disconnect, device number 2
[ 1081.832158] usb 1-1: new high-speed USB device number 3 using xhci-hcd
[ 1081.969792] usb 1-1: New USB device found, idVendor=2357, idProduct=011e, bcdDevice= 2.00
[ 1081.969808] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1081.969819] usb 1-1: Product: 802.11ac WLAN Adapter
[ 1081.969827] usb 1-1: Manufacturer: Realtek
[ 1081.969836] usb 1-1: SerialNumber: 00e04c000001
[ 1082.194843] usb 1-1: 88XXau 10:5a:95:c7:9e:69 hw_info[107]
[ 1082.911593] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1082.911656] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
```

## Reply by Alex Kushleyev (ModalAI staff) · 2026-04-03 18:21:28 UTC (in reply to Alex Kushleyev)

Also, here is output of `tail -n 100 /var/log/syslog`:

```
Apr  3 18:17:22 m0054 dhcpcd[2755]: wlan0: carrier lost
Apr  3 18:17:22 m0054 wpa_supplicant[1996]: wlan0: CTRL-EVENT-DISCONNECTED bssid=5c:e9:31:0a:78:23 reason=3 locally_generated=1
Apr  3 18:17:22 m0054 kernel: [  402.693093] RTW: rtw_ndev_uninit(wlan0) if1
Apr  3 18:17:22 m0054 systemd[1]: Starting Load/Save RF Kill Switch Status...
Apr  3 18:17:22 m0054 systemd-rfkill[4368]: Failed to open device rfkill3: No such device
Apr  3 18:17:22 m0054 systemd[1]: Started Load/Save RF Kill Switch Status.
Apr  3 18:17:22 m0054 dhcpcd[2755]: wlan0: deleting address fe80::5c1e:5176:405d:82d8
Apr  3 18:17:22 m0054 dhcpcd[2755]: wlan0: deleting default route via 192.168.10.1
Apr  3 18:17:22 m0054 dhcpcd[2755]: wlan0: deleting route to 192.168.10.0/24
Apr  3 18:17:22 m0054 dhcpcd[2755]: wlan0: removing interface
Apr  3 18:17:29 m0054 kernel: [  409.880457] usb 1-1: new high-speed USB device number 5 using xhci-hcd
Apr  3 18:17:30 m0054 kernel: [  410.369086] RTW: HW EFUSE
Apr  3 18:17:30 m0054 kernel: [  410.369100] RTW: 0x000: 29 81 00 BC  09 00 21 00  6E 04 A4 34  10 00 30 0B  
Apr  3 18:17:30 m0054 kernel: [  410.369142] RTW: 0x010: 26 26 26 26  26 26 27 27  27 27 27 13  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.369221] RTW: 0x030: 13 FF FF FF  FF FF E0 FF  FF FF 28 28  28 28 28 28  
Apr  3 18:17:30 m0054 kernel: [  410.369299] RTW: 0x050: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.369377] RTW: 0x070: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.369454] RTW: 0x090: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.369532] RTW: 0x0B0: FF FF FF FF  FF FF FF FF  7F 1A 1B 00  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.369609] RTW: 0x0D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.369687] RTW: 0x0F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.369764] RTW: 0x110: 65 61 6C 74  65 6B 0E 03  38 30 32 2E  31 31 61 63  
Apr  3 18:17:30 m0054 kernel: [  410.369842] RTW: 0x130: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.369920] RTW: 0x150: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.369997] RTW: 0x170: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.370075] RTW: 0x190: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.370153] RTW: 0x1B0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.370230] RTW: 0x1D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.370308] RTW: 0x1F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr  3 18:17:30 m0054 kernel: [  410.562635] RTW: [RF_PATH] ver_id.RF_TYPE:RF_1T1R
Apr  3 18:17:30 m0054 kernel: [  410.562646] RTW: [RF_PATH] HALSPEC's rf_reg_trx_path_bmp:0x11, rf_reg_path_avail_num:1, max_tx_cnt:1
Apr  3 18:17:30 m0054 kernel: [  410.562653] RTW: [RF_PATH] PG's trx_path_bmp:0x00, max_tx_cnt:0
Apr  3 18:17:30 m0054 kernel: [  410.562665] RTW: [RF_PATH] HALDATA's trx_path_bmp:0x11, max_tx_cnt:1
Apr  3 18:17:30 m0054 kernel: [  410.562680] RTW: [TRX_Nss] HALSPEC - tx_nss:1, rx_nss:1
Apr  3 18:17:30 m0054 kernel: [  410.562686] RTW: [TRX_Nss] Registry - tx_nss:0, rx_nss:0
Apr  3 18:17:30 m0054 kernel: [  410.562691] RTW: [TRX_Nss] HALDATA - tx_nss:1, rx_nss:1
Apr  3 18:17:30 m0054 kernel: [  410.562700] RTW: txpath=0x1, rxpath=0x1
Apr  3 18:17:30 m0054 kernel: [  410.562707] RTW: txpath_1ss:0x1, num:1
Apr  3 18:17:30 m0054 kernel: [  410.563928] RTW: rtw_regsty_chk_target_tx_power_valid return _FALSE for band:0, path:0, rs:0, t:-1
Apr  3 18:17:30 m0054 kernel: [  410.567269] RTW: rtw_ndev_init(wlan0) if1 mac_addr=00:c0:ca:b3:a4:ec
Apr  3 18:17:30 m0054 systemd[1]: Starting Load/Save RF Kill Switch Status...
Apr  3 18:17:30 m0054 systemd-rfkill[4511]: Failed to parse state file /var/lib/systemd/rfkill/platform-xhci-hcd.0.auto-usb-0:1:1.2:wlan: Invalid argument
Apr  3 18:17:30 m0054 systemd[1]: Started Load/Save RF Kill Switch Status.
Apr  3 18:17:31 m0054 dhcpcd[2755]: wlan0: waiting for carrier
Apr  3 18:17:31 m0054 systemd-udevd[4512]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr  3 18:17:36 m0054 kernel: [  416.679144] RTW: wlan0- hw port(0) mac_addr =00:c0:ca:b3:a4:ec
Apr  3 18:17:36 m0054 wpa_supplicant[1996]: wlan0: Trying to associate with 5c:e9:31:0a:78:24 (SSID='xxxxxx' freq=5200 MHz)
Apr  3 18:17:36 m0054 wpa_supplicant[1996]: FT: Invalid key management type (2)
Apr  3 18:17:36 m0054 kernel: [  416.734679] RTW: rtw_set_802_11_connect(wlan0)  fw_state=0x00000008
Apr  3 18:17:36 m0054 kernel: [  416.868146] RTW: start auth
Apr  3 18:17:36 m0054 kernel: [  416.871600] RTW: auth success, start assoc
Apr  3 18:17:36 m0054 kernel: [  416.883349] RTW: assoc success
Apr  3 18:17:36 m0054 wpa_supplicant[1996]: wlan0: Associated with 5c:e9:31:0a:78:24
Apr  3 18:17:36 m0054 wpa_supplicant[1996]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr  3 18:17:36 m0054 kernel: [  416.888060] RTW: curr_tx_rate : CCK_1M (L)
Apr  3 18:17:36 m0054 kernel: [  416.888070] RTW: curr_retry_ratio : 0
Apr  3 18:17:36 m0054 kernel: [  416.888075] RTW: ra_mask : 0x00000000003ffff0
Apr  3 18:17:36 m0054 kernel: [  416.898522] RTW: recv eapol packet 1/4
Apr  3 18:17:36 m0054 wpa_supplicant[1996]: wlan0: WPA: Key negotiation completed with 5c:e9:31:0a:78:24 [PTK=CCMP GTK=CCMP]
Apr  3 18:17:36 m0054 wpa_supplicant[1996]: wlan0: CTRL-EVENT-CONNECTED - Connection to 5c:e9:31:0a:78:24 completed [id=0 id_str=]
Apr  3 18:17:36 m0054 kernel: [  416.925772] RTW: set group key camid:1, addr:5c:e9:31:0a:78:24, kid:1, type:AES
Apr  3 18:17:36 m0054 dhcpcd[2755]: wlan0: carrier acquired
Apr  3 18:17:36 m0054 dhcpcd[2755]: wlan0: IAID ca:b3:a4:ec
Apr  3 18:17:36 m0054 dhcpcd[2755]: wlan0: adding address fe80::5c1e:5176:405d:82d8
Apr  3 18:17:37 m0054 dhcpcd[2755]: wlan0: soliciting an IPv6 router
Apr  3 18:17:37 m0054 dhcpcd[2755]: wlan0: rebinding lease of 192.168.10.179
Apr  3 18:17:37 m0054 dhcpcd[2755]: wlan0: truncated packet (179) from 127.0.0.1
Apr  3 18:17:37 m0054 dhcpcd[2755]: wlan0: truncated packet (207) from 127.0.0.1
Apr  3 18:17:37 m0054 dhcpcd[2755]: wlan0: probing address 192.168.10.179/24
Apr  3 18:17:42 m0054 dhcpcd[2755]: wlan0: leased 192.168.10.179 for 7200 seconds
Apr  3 18:17:42 m0054 dhcpcd[2755]: wlan0: adding route to 192.168.10.0/24
Apr  3 18:17:42 m0054 dhcpcd[2755]: wlan0: adding default route via 192.168.10.1
Apr  3 18:17:50 m0054 dhcpcd[2755]: wlan0: no IPv6 Routers available
```

## Reply by Alex Kushleyev (ModalAI staff) · 2026-04-03 18:25:11 UTC (in reply to Alex Kushleyev)

@SKA , please check the output of syslog, it may contain a hint as to why wlan0 has a static ip, maybe dhcpcd is not working properly.

## Reply by SKA · 2026-04-03 18:26:04 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev When I run ```tail -n 100 /var/log/syslog```, I don't see any messages coming from ```m0104 dhcpcd``` or ```m0104 wpa_supplicant```

edit: I turned the USB VBUS off and on, and saw this pop up on syslog: 
```
Apr  3 16:07:44 m0104 dhcpcd[2276]: wlan0: probing for an IPv4LL address
```

## Reply by Alex Kushleyev (ModalAI staff) · 2026-04-03 18:33:06 UTC (in reply to SKA)

@SKA , can you also please check `journalctl -u dhcpcd` to see if there is anything interesting there?

```
Apr 03 18:10:27 m0054 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support...
Apr 03 18:10:27 m0054 dhcpcd[1982]: grep: /etc/network/interfaces: No such file or directory
Apr 03 18:10:28 m0054 dhcpcd[2095]: DUID 00:01:00:01:2b:93:59:dc:ea:a6:9f:04:b1:61
Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: IAID ca:b3:a4:ec
Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: adding address fe80::10c0:dcc6:145e:c4cd
Apr 03 18:10:28 m0054 dhcpcd[2095]: bond0: waiting for carrier
Apr 03 18:10:28 m0054 dhcpcd[2095]: dummy0: waiting for carrier
Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: carrier lost
Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: deleting address fe80::10c0:dcc6:145e:c4cd
Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: carrier acquired
Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: IAID ca:b3:a4:ec
Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: adding address fe80::10c0:dcc6:145e:c4cd
Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: carrier lost
Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: deleting address fe80::10c0:dcc6:145e:c4cd
Apr 03 18:10:28 m0054 dhcpcd[2095]: dummy0: carrier acquired
Apr 03 18:10:28 m0054 dhcpcd[2095]: dummy0: IAID 5b:b6:cf:20
Apr 03 18:10:28 m0054 dhcpcd[2095]: dummy0: adding address fe80::8837:2803:320d:3a20
Apr 03 18:10:29 m0054 dhcpcd[2095]: dummy0: soliciting a DHCP lease
Apr 03 18:10:29 m0054 dhcpcd[2095]: dummy0: soliciting an IPv6 router
Apr 03 18:10:34 m0054 dhcpcd[2095]: wlan0: carrier acquired
Apr 03 18:10:34 m0054 dhcpcd[2095]: wlan0: IAID ca:b3:a4:ec
Apr 03 18:10:35 m0054 dhcpcd[2095]: wlan0: soliciting an IPv6 router
Apr 03 18:10:35 m0054 dhcpcd[2095]: wlan0: rebinding lease of 192.168.10.179
Apr 03 18:10:35 m0054 dhcpcd[2095]: wlan0: probing address 192.168.10.179/24
Apr 03 18:10:40 m0054 dhcpcd[2095]: wlan0: leased 192.168.10.179 for 7200 seconds
Apr 03 18:10:40 m0054 dhcpcd[2095]: wlan0: adding route to 192.168.10.0/24
Apr 03 18:10:40 m0054 dhcpcd[2095]: wlan0: adding default route via 192.168.10.1
Apr 03 18:10:40 m0054 dhcpcd[2095]: forked to background, child pid 2755
Apr 03 18:10:40 m0054 systemd[1]: Started LSB: IPv4 DHCP client with IPv4LL support.
Apr 03 18:10:41 m0054 dhcpcd[2755]: dummy0: no IPv6 Routers available

```

## Reply by SKA · 2026-04-03 18:39:03 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev Here's what I see! I wonder if this is the problem: 
```
/etc/network/interfaces: No such file or directory
```
```
voxl2-mini (M0104):/$ journalctl -u dhcpcd
-- Logs begin at Thu 2023-03-02 12:58:02 UTC, end at Fri 2026-04-03 16:11:48 UTC. --
Mar 02 12:58:04 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support...
Mar 02 12:58:04 m0104 dhcpcd[1250]: grep: /etc/network/interfaces: No such file or directory
Mar 02 12:58:05 m0104 dhcpcd[1309]: no interfaces have a carrier
Mar 02 12:58:05 m0104 dhcpcd[1309]: forked to background, child pid 1503
Mar 02 12:58:05 m0104 systemd[1]: Started LSB: IPv4 DHCP client with IPv4LL support.
Mar 02 12:58:06 m0104 dhcpcd[1503]: bond0: waiting for carrier
Mar 02 12:58:06 m0104 dhcpcd[1503]: dummy0: waiting for carrier
Mar 02 12:58:06 m0104 dhcpcd[1503]: wlan0: waiting for carrier
Mar 02 12:58:06 m0104 dhcpcd[1503]: dummy0: carrier acquired
Mar 02 12:58:06 m0104 dhcpcd[1503]: DUID 00:01:00:01:2b:93:59:de:b6:a9:9d:64:6d:02
Mar 02 12:58:06 m0104 dhcpcd[1503]: dummy0: IAID 9d:64:6d:02
Mar 02 12:58:06 m0104 dhcpcd[1503]: dummy0: adding address fe80::54fe:595c:4ff6:b95c
Mar 02 12:58:06 m0104 dhcpcd[1503]: dummy0: soliciting a DHCP lease
Mar 02 12:58:07 m0104 dhcpcd[1503]: dummy0: soliciting an IPv6 router
Mar 02 12:58:10 m0104 dhcpcd[1503]: wlan0: carrier acquired
Mar 02 12:58:10 m0104 dhcpcd[1503]: wlan0: IAID ca:b3:a6:89
Mar 02 12:58:10 m0104 dhcpcd[1503]: wlan0: adding address fe80::bc34:9301:bd06:6b68
Mar 02 12:58:11 m0104 dhcpcd[1503]: wlan0: soliciting a DHCP lease
Mar 02 12:58:11 m0104 dhcpcd[1503]: wlan0: soliciting an IPv6 router
Mar 02 12:58:12 m0104 dhcpcd[1503]: wlan0: offered 10.10.10.116 from 10.10.10.1
Mar 02 12:58:12 m0104 dhcpcd[1503]: wlan0: probing address 10.10.10.116/24
Mar 02 12:58:17 m0104 dhcpcd[1503]: wlan0: leased 10.10.10.116 for 86400 seconds
Mar 02 12:58:17 m0104 dhcpcd[1503]: wlan0: adding route to 10.10.10.0/24
Mar 02 12:58:17 m0104 dhcpcd[1503]: wlan0: adding default route via 10.10.10.1
Mar 02 12:58:19 m0104 dhcpcd[1503]: dummy0: no IPv6 Routers available
Mar 02 12:58:24 m0104 dhcpcd[1503]: wlan0: no IPv6 Routers available
-- Reboot --
Apr 03 15:39:02 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support...
Apr 03 15:39:02 m0104 dhcpcd[1899]: grep: /etc/network/interfaces: No such file or directory
Apr 03 15:39:03 m0104 dhcpcd[2026]: no interfaces have a carrier
Apr 03 15:39:03 m0104 dhcpcd[2262]: bond0: waiting for carrier
Apr 03 15:39:03 m0104 dhcpcd[2262]: dummy0: waiting for carrier
Apr 03 15:39:03 m0104 dhcpcd[2262]: wlan0: waiting for carrier
Apr 03 15:39:03 m0104 dhcpcd[2262]: dummy0: carrier acquired
Apr 03 15:39:03 m0104 dhcpcd[2026]: forked to background, child pid 2262
Apr 03 15:39:03 m0104 systemd[1]: Started LSB: IPv4 DHCP client with IPv4LL support.
Apr 03 15:39:03 m0104 dhcpcd[2262]: DUID 00:01:00:01:2b:93:59:de:b6:a9:9d:64:6d:02
Apr 03 15:39:03 m0104 dhcpcd[2262]: dummy0: IAID 7e:3c:18:e8
Apr 03 15:39:03 m0104 dhcpcd[2262]: dummy0: adding address fe80::e48d:a57d:cf5f:95ce
Apr 03 15:39:03 m0104 dhcpcd[2262]: dummy0: soliciting an IPv6 router
Apr 03 15:39:04 m0104 dhcpcd[2262]: dummy0: soliciting a DHCP lease
Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: carrier acquired
Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: IAID ca:b3:a6:89
Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: adding address fe80::bc34:9301:bd06:6b68
Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: soliciting a DHCP lease
Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: offered 10.10.10.116 from 10.10.10.1
Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: probing address 10.10.10.116/24
Apr 03 15:39:13 m0104 dhcpcd[2262]: wlan0: soliciting an IPv6 router
Apr 03 15:39:15 m0104 dhcpcd[2262]: dummy0: no IPv6 Routers available
Apr 03 15:39:17 m0104 dhcpcd[2262]: wlan0: leased 10.10.10.116 for 86400 seconds
Apr 03 15:39:17 m0104 dhcpcd[2262]: wlan0: adding route to 10.10.10.0/24
Apr 03 15:39:17 m0104 dhcpcd[2262]: wlan0: adding default route via 10.10.10.1
Apr 03 15:39:26 m0104 dhcpcd[2262]: wlan0: no IPv6 Routers available
-- Reboot --
Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support...
-- Reboot --
Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support...
-- Reboot --
Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support...
-- Reboot --
Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support...
-- Reboot --
Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support...
-- Reboot --
Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support...
-- Reboot --
Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support...
-- Reboot --
--More--
```

## Reply by Alex Kushleyev (ModalAI staff) · 2026-04-03 18:47:53 UTC (in reply to SKA)

@SKA ,

I have the same same error, but wifi is working (`/etc/network/interfaces: No such file or directory`). 

I also see that your dhcp client is able to get an ip address 10.10.10.116 for wlan0, which is strange that you don't see that ip address in `ifconfig`..

## Reply by Alex Kushleyev (ModalAI staff) · 2026-04-03 18:57:19 UTC (in reply to Alex Kushleyev)

can you please check output of `ifconfig` ? i wonder if wlan0 is not the primary interface for some reason

## Reply by SKA · 2026-04-03 19:00:20 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev 
```
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2312
        inet 169.254.233.208  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::ddc:47bd:f5ec:71dd  prefixlen 64  scopeid 0x20<link>
        ether 10:5a:95:c7:9e:69  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 30 overruns 0  carrier 0  collisions 0
```

## Reply by Alex Kushleyev (ModalAI staff) · 2026-04-03 19:08:11 UTC (in reply to SKA)

@SKA , thank you for providing all the information. We are doing more testing and will get back to you. So far cannot reproduce.

Alex

## Reply by Matt69 · 2026-05-08 13:55:57 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev I reflashed 1.6.3 on the VOXL 2 twice and it seemed to fix it the second time. Weird that it fixed it and I am also unable to reproduce the issue again. At least it works now lol.