Bypass, Connection-mode – Brocade Mobility RFS Controller CLI Reference Guide (Supporting software release 5.5.0.0 and later) User Manual
Page 198
![background image](/manuals/361696/198/background.png)
182
Brocade Mobility RFS Controller CLI Reference Guide
53-1003098-01
4
Related Commands:
bypass
Enables bypassing of captive portal detection requests from wireless clients
Certain devices, such as Apple IOS devices send Captive Network Assistant (CNA) requests to
detect existence of captive portals. When enabled, the bypass option does not allow CNA requests
to be redirected to the captive portal pages.
Supported in the following platforms:
•
Access Points — Brocade Mobility 650 Access Point, Brocade Mobility 6511 Access Point,
Brocade Mobility 1220 Access Point, Brocade Mobility 71XX Access Point, Brocade
Mobility 1240 Access Point
•
Wireless Controllers — Brocade Mobility RFS4000, Brocade Mobility RFS6000, Brocade
Mobility RFS7000
•
Service Platforms — Brocade Mobility RFS9510
Syntax:
bypass captive-portal-detection
Parameters
bypass captive-portal-detection
Example
rfs4000-229D58(config-captive-portal-test)#bypass captive-portal-detection
rfs4000-229D58(config-captive-portal-test)#show context
captive-portal test
bypass captive-portal-detection
rfs4000-229D58(config-captive-portal-test)#
Related Commands:
connection-mode
Configures a captive portal’s mode of connection to the Web server. HTTP uses plain unsecured
connection for user requests. HTTPS uses an encrypted connection to support user requests.
Both HTTP and HTTPS use the same Uniform Resource Identifier (URI), so controller and client
resources can be identified. However. Brocade recommends the use of HTTPS, as it affords
controller and client transmissions some measure of data protection HTTP cannot provide.
Supported in the following platforms:
Disables accounting records for this captive portal
bypass
captive-portal-detection
Bypasses captive portal detection requests
Disables bypassing of captive portal detection requests