Captive Portal Redirection (S-, K-Series)

Captive Portal Redirection uses HTTP redirection to force a client‘s web browser to be redirected to a particular administrative web page. A network administrator can use this feature for such web based contexts as redirecting to a page for purposes of:

Captive Portal Redirection is an extension of the Policy feature. Policy roles can be configured to force redirection of HTTP traffic by specifying a web redirection class index which associates with it up to two redirection servers. The HTTP traffic to potentially be redirected is identified based upon a destination captive portal server absolute URL address containing an IPv4 address, TCP port, and path. For traffic that is placed into one of these policy roles (through authentication or policy admin-profile rules) actions will be taken based upon the contents of the policy profile. If the incoming traffic is on the configured L4 port and is not destined for the configured captive portal server IP, the switch will cause an HTTP redirect message (code 307) to be sent back to the client. If the incoming traffic is destined for the configured captive portal server IP, or it is not on one of the configured listening L4 ports, it will be handled according to the rest of the policy role configuration.

When configuring Captive Portal Redirection, the administrator can globally configure up to three ports on which policy on this device listens for client traffic that may be subject to HTTP redirection. Captive Portal Redirection provides for the configuration of up to ten web-redirect groups of captive portal servers. These web-redirect groups are identified by associating a web redirection class index with the server ID. A URL that explicitly identifies the server by an IPv4 address, TCP port, and path is configured along with the ports on which the Captive Portal feature listens for client traffic.

The Captive Portal Redirection policy roles are configured for a web-redirect group. By default, the policy profile web-redirect index is unset and has a numeric value of 0. To enable Captive Portal Redirection there must be a policy role (profile) defined that has a valid captive portal web redirection class index value of 1 – 10. In addition to the captive portal configuration, this policy role should also have rules to handle the traffic that would not be handled by Captive Portal Redirection.

The URL for the captive portal server must:

In the following example: