Hi, @ArthurC
We have run the setup for more than 2 days using nmcli but we are not observed the "disassociation" issue which you have reported.
So, It looks like the issue is only observed at your environment.
For further debugging we need at least one set of debug logs of the wpa_supplicant because the nmcli is using the wpa_supplicant in background,
You can use below steps to enable the supplicant logs:
1. boot up the board
2. killall wpa_supplicant
3. open "vi /lib/systemd/system/wpa_supplicant.service"
4. add -ddd at end "ExecStart=/usr/sbin/wpa_supplicant -u -ddd"
5. reboot the board
6. Run the scenario using nmcli
7. run journalctl -a -b to capture the supplicant logs
Please use drvdbg=0xa0037 while running the scenario.
If you use drvdbg=0xa0037, device will hang, then you can also use the drvdbg=0x80037.
But make sure to take the dump manually using below commands after the crash is observed.
- echo "debug_dump" >/proc/mwlan/adapter0/config
- cat /proc/mwlan/adapter0/drv_dump > file_drv_dump
- cat /proc/mwlan/adapter0/fw_dump > file_fw_dump
Share the journalctl/console and dmesg logs for further debugging.
Kindly help to get the requested logs to unblock the debugging.
Please note: We need this logs ASAP to conclude the issue, If you are not supporting then we could not support this case further. Because we must need the supplicant logs to further narrow down the issue.
Best Regards,
Christine.