Acceptance policy expatriation

[patkszen]

We have guest wifi setup with captive portal + user acceptance policy. It seems after sometime time of inactivity clients are being prompted to accept UAP again. It causes some issues for clients using VPN.

Is there a timer responsible for this and can it be adjusted?

HM Classic 8.1r2, AP'a 130 HiveOS 8.1r2a

[samantha_lynn]

Roaming Cache Ageout is actually the number of times a client can be absent from updates from neighboring APs. So with the default setting of 60 we see in your screenshot, if a client leaves the network, and is away for 60 consecutive updates from this AP or neighboring APs, it will be removed from the roaming cache. This means you'd want to set the Roaming Cache Update Interval to determine how often these updates from neighbors occur, and then you can set the number of updates the user can be absent for in the Roaming Cache Ageout.

This page goes in to more detail on these settings, if you're interested: docs.aerohive.com/330000/docs/help/english/8.2r2/hm/full/Content/config/ssid/ssidSet.htm

[patkszen]

thanks Sam, I will give this a go

I assume Roaming Cache Ageout value is in minutes

[samantha_lynn]

Yes, if you go to Configuration> Open the Network Policy> Open the CWP object in use> Expand Optional Additional Settings> find the registration period. Here we can set the length of time that a registered user with an active session remains registered. If the user closes one session and later starts a new one while the AP still has a roaming cache entry for their client (one hour by default), they will not have to register with the captive web portal again. On the other hand, if the user closes a session and then starts a new session after the roaming cache entry has been removed, they must complete the registration process again even if the new session begins within the registration period. 

You can adjust the roaming cache time by opening the SSID> Expanding Advanced> adjust the Roaming Cache times.