You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 1, 2023. It is now read-only.
after a while of being connected, sometimes wsupp stops working, while the process stays active.
when this happens, wifi shows the AP as "idle" in the bottom line of status display, but the AP itself is not listed. when i then do wifi scan, the AP then shows up in the list, with a * next to its name, but wsupp still doesn't connect to it.
i suspect this happens when, after the disconnect happens, the AP is momentarily not in the scan results of the scan done by wsupp itself. i believe this to be so because i noticed on other disconnects (watching the output of my dhcp replacement script) wsupp immediately connects again.
this happens also when i use the minibase wsupp, it is probably due to me not using the ifmon tool, yet i think since on some disconnects reconnect works, it is the intention of the program to always re-establish the connection, which makes sense (alternatively, wsupp could exit, so the service supervisor would automatically restart it).
The text was updated successfully, but these errors were encountered:
On disconnect, wsupp scans the frequency the AP was on immediately. If the AP were there, it would re-connect, but in this case AP was not there. It will then continue re-scanning that frequency every 10s and also do full scans once in a while, waiting for the AP to re-appear.
The idea behind this was to handle AP reboots. However, from description, it looks like you're actually losing the radio link for a brief time, enough to trigger disconnect and miss the first re-scan. And 10s timeout until the next re-scan is likely too long in this case.
Unlikely but there may be something useful in in dmesg. If possible, try waiting about 10 seconds after it drops connect to see if it re-connects on the second attempt. If it won't, something else must be wrong.
The * means saved PSK is available for this AP. No reconnect on wifi scan is intentional, it's really confusing when you're asking it to scan and it connects instead. wifi ap $ssid should connect immediately. It really calls for a new command, something like wifi retry.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
after a while of being connected, sometimes wsupp stops working, while the process stays active.
when this happens,
wifi
shows the AP as "idle" in the bottom line of status display, but the AP itself is not listed. when i then dowifi scan
, the AP then shows up in the list, with a*
next to its name, but wsupp still doesn't connect to it.i suspect this happens when, after the disconnect happens, the AP is momentarily not in the scan results of the scan done by wsupp itself. i believe this to be so because i noticed on other disconnects (watching the output of my
dhcp
replacement script) wsupp immediately connects again.this happens also when i use the minibase wsupp, it is probably due to me not using the
ifmon
tool, yet i think since on some disconnects reconnect works, it is the intention of the program to always re-establish the connection, which makes sense (alternatively, wsupp could exit, so the service supervisor would automatically restart it).The text was updated successfully, but these errors were encountered: