@istong wrote:
HI,
I have mine set at - aaa timers idle-timeout 1200 seconds. It was mentioned by cjoseph this can cause problems if set too high. What are those problems and is there a workaround?
Also kdisc98 mentioned keeping the dhcp timers (lease time) = to this idle-timeout. What or where specifically are you referring to for the dhcp timers? Our DHCP is handed out by a windows server for all but the guest wifi/captive portal users which get theirs from the controller.
Thanks
If set too high, clients stay in the user table much longer than they do actually, giving you an inflated view of your users. In addition, if you are using IP spoofing protection, it would seem that users still have an ip address, even though they are long gone. It should definitely not be longer than your DHCP scope lease, but longer than the default creates an inaccurate view of how many users are connected.