Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

Wireless clients forced to accept captive portal Terms and Conditions on every roam

« Go Back

Information

 
TitleWireless clients forced to accept captive portal Terms and Conditions on every roam
Objective
Wireless clients always being redirected on captive portal WLAN when roaming, resulting in user to accept Terms and Condition page each time client roams.
Environment
  • WirelessWiNG
  • WiNG v5
  • WiNG 5
  • RFS6010
  • RFS7010
  • RFS40xx
  • NX9XXX
  • NX75XX/NX75XX-E
  • NX65XX/NX45XX
  • NX55XX/NX55XX-E
  • AP8432
  • AP8533
  • AP82XX
  • AP75XX
  • AP7522-E
  • AP7502-E
  • AP76XX
  • AP71x1
  • AP65xx
  • AP650
  • AP62x
  • AP8132
Procedure
Must configure the WLAN wireless-client hold-time to match the captive poral inactivity-timeout. These steps need to be performed via the wireless controller CLI. 

By default, captive portal client settings/inactivity timeout is 10 minutes.
By default, the WLAN wireless-client hold-time is 30 seconds

If using the default captive portal client settings, the WLAN wireless-client hold-time needs to match. Same is true if modification of the captive client settings is performed. 

The following example is if the default captive portal client settings/inactivity timeout (10 minutes) is being used.

Log into the wireless controller CLI (Command Line Interface) and perform the following:

enable [enter]
config [enter]
wlan xxxxx [enter] (x represents WLAN name being modified. Use tab to show available WLANs. If only one WLAN is configured, tab will auto-fill WLAN name)
wireless-client hold-time 600 [enter] (600 seconds equals 10 minutes)
com wr [enter] (this saves running to startup)

The above should be considered best practices for captive portal deployments using Terms and Conditions. 
 
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255