08-07-2014 11:38 PM - edited 07-05-2021 01:20 AM
Hello,
08-08-2014 12:42 AM
make sure that the session timeout is greater than the client idle timeout, otherwise the sleeping client entry would not be created.
After entering the appropriate login credentials for web-auth, the client get authenticated and moves to RUN state.
Now if the client configured is idle for 300 seconds (default idle timeout value) or disconnects from the WLAN it is connected to, then the client will move to sleeping clients.
Once the client is moved to the Sleeping Clients, the timeout session starts and the remaining time before the client entry is deleted/cleared is displayed.
If the client wakes up or joins back to the same WLAN, it doesn't require re-authentication.
the number of sleeping clients that are remembered has increased to 25000 from the previous 9000. A larger number of sleeping clients are remembered even after waking up, on the wireless network with high-scale Cisco WLCs. This eliminates the need for user intervention to re-enter credentials for a greater number of clients.
08-08-2014 03:25 AM
Thanks for the answer.
However with the idle timeout set to 14400 seconds I can already achieve the same behaviour as sleeping client.
For example my client associates and authenticates against the web portal at time X. At time X+60s the client goes to sleep.
When the client wakes up and re-associates at time X + 3600s it is still in the client database and doesn't have to authenticate.
So i was wondering if the sleeping client feature was usefull when the idle timeout can play that role.
10-11-2018 10:33 PM
Hi Maxime,
You will see the difference when the client wakes up and re-associates at time X + 14400s(user idle timeout), this time the client has to reauthenticate. That way you will understand the usage of sleeping client.
Thanks
Sreejith
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide