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
For static devices, most of the time, connection loss is due to AP reboot or power failure.
In that situation, you mostly just want to reconnect to the AP as soon as it is back online and avoid long timeouts.
My I suggest the following behaviour: (I am thinking non-blocking )
When portal is automatically started because of AP connection loss, run every N seconds a passive scan for APs in the background .
When the AP is available again and no-one is connected to the portal, close the portal and reconnect to AP immediately.
Hope you will consider,
The text was updated successfully, but these errors were encountered:
@alka79 Did you figure out a way to get this working? I'm trying to achieve a similar thing and having no luck. Don't suppose you came up with a work-around?
For static devices, most of the time, connection loss is due to AP reboot or power failure.
In that situation, you mostly just want to reconnect to the AP as soon as it is back online and avoid long timeouts.
My I suggest the following behaviour: (I am thinking non-blocking )
When portal is automatically started because of AP connection loss, run every N seconds a passive scan for APs in the background .
When the AP is available again and no-one is connected to the portal, close the portal and reconnect to AP immediately.
Hope you will consider,
The text was updated successfully, but these errors were encountered: