05-31-2018 07:30 AM
Hello,
I am working on a quest portal to replace the captive portal on our WLAN controllers. One question that came up is that what can we do about unregistered users who are just walking by and happen to associate with SSID we setup for the guest portal but we want to kick them off after a certain amount of time. We don't want our DHCP space taken up by those who are registered users. Should this be part of the redirect authorization policy or on the controller?
Solved! Go to Solution.
05-31-2018 08:07 AM
Can you please explain further what the problem is and how you want to work.
If somebody is automatically connecting to an open network then the only way to stop it is to secure that network, we recommend using WPAPSK to accomplish this.
the wireless controller User idle time out is 180 seconds this means when they leave the network the session will only stay pinned up for a max of three minutes.
if you’re worried about DHCP IP addresses being exhausted and don’t want to lock down the SSID then you can adjust your lease time
05-31-2018 08:07 AM
Can you please explain further what the problem is and how you want to work.
If somebody is automatically connecting to an open network then the only way to stop it is to secure that network, we recommend using WPAPSK to accomplish this.
the wireless controller User idle time out is 180 seconds this means when they leave the network the session will only stay pinned up for a max of three minutes.
if you’re worried about DHCP IP addresses being exhausted and don’t want to lock down the SSID then you can adjust your lease time
05-31-2018 09:27 PM
This is handled by two things
I have not had much luck with Cisco WLC's and Session-Idle-Timeout - but the Session-Timeout is an absolute value (in seconds) and this works like a charm
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