changing wpa_supplicant.wlan0.conf
Closed this issue · 5 comments
Hi gitbls , hope your still here.
autoAP is nice , got one issue im currently trying to finalize. It's not entirely in scope but maybe you know..
- I remove the first networked from wpa_supplicant.wlan0.conf. Forcing AP mode.
- Let '' user '' send ssid and psk over custom udp socket.
- Overwrite wpa_supplicant.wlan0.conf with new proper one, including those ssid and psk
To instantly reconfigure stuff, next call:
sudo wpa_cli -i wlan0 reconfigure
after that, most common things are cool:
- AP to STA/client
- STA/client back to AP
- AP to a 'non existing SSID' -> falls instantly back to autoAP ( .. works out well )
However - when i update wpa_supplicant.wlan0.conf with a good SSID but a wrong password it blows up. The system seems to go for STA/client mode, with Access Point: Non-Associated and a broken connection. Did not fall back into AP mode.
Current solution i have is launching a second script checking for any connection, then write back supplicant.wlan0.conf as described in (1) , followed by reconfigure, to rescue the system. A complete system reboot would make it fall to AP too, but takes longer.
Anything you know or direct call i could do on autoAP to 'fix' this one more elegant?
Wow, I'm really sorry! Somehow I completely missed this issue. :( I'll take a look at this when I have a few minutes and update with my findings/suggestions.
I spent some time looking at this, and don't have any great suggestions for how to address. Might want to post the question on the WPA Supplicant mailing list
hey gitbls
thanks for taking a look and your suggestion ,
i have been looking at it quite some times but im not sure what is going on but its not coming from autoAP.
it is working 'ok' for now , with the mentioned rescue script checking for 'Non-Associated' state, and then rollback to AP.
Can you post your 'rescue' script? Might be possible to modify autoAP to watch for the bad status and do something about it.