Hi Patrick - it's happened again. This time I unplugged the Wifi adapter and plugged it in again - the SBC connected successfully to the network. I checked the processes running: wpa_supplicant and wpa_cli were both on the process list
Code: Select all
4089 root S 712 /usr/sbin/wpa_supplicant -iwlan0 -c/mnt/userspace/.config/wpa_supplicant.conf -P/var/run/wpa_supplicant_wlan0.pid -B
4091 root S 444 /usr/sbin/wpa_cli -iwlan0 -a/sbin/wpa_action -P/var/run/wpa_cli_wlan0.pid -B
I then power cycled the SBC. The full process list before and after the power cycle is available athttp://www.hinch.me.uk/Processes.txt
It strikes me that there may be issues with the Wifi adapter, perhaps confirmed by the fact that the one supplied with my second SBC had to be replaced under warranty? I look forward to hearing your comments.
Given that my program periodically checks for network availability, is there any way of rebooting the Wifi adapter under program control?