If the data sent by the client is more than the threshold quota specified within the user idle timeout, the client is considered to be active and the controller refreshes for another timeout period. You can also configure a threshold triggered timeout where if a client has not sent a threshold quota of data within the specified user idle timeout, the client is considered to be inactive and is deauthenticated.
POTATO MUSH CLIENT 2.0.16 FREE
Our corporate bigwigs want the ease of use of the Open WLAN (most of our clients are not employees, we offer free wi-fi for our guests) but I need to figure out a way to keep the AP load managable and knock these non-authenticated off the system.
So if you have your Timeout set to 1 hour, and your Threshold set to 0 (default), then the system will allow that client to remain associated for the entire hour while passing no traffic.Īm I interpretting those settings correctly? My understanding of the Client User Idle Threshold is the measure of data that must pass from the client during the Client User Idle timeout window. We see dozens of clients associated to each AP, but the throughput is a few hundred bytes and they are sitting at a WEBAUTH_REQD state. So, since this is an open SSID, we see hundreds of clients that come to our facility and their devices pick up the SSID and associate to it, but the client never opens a browser to accept the T&C's. In our deployment, our Guest SSID is open with just a Web Passthrough that offers up Terms and Conditions. I just ran across this thread and have a slight twist on the timer question.
0 kommentar(er)
