Captive Portal was designed to give temporary users limited network access while preventing them from seeing company-private programs and information. For example, visitors to a school football stadium may have wireless access to a Captive Portal that lets them use only the Internet. Before configuring Captive Portal, create a corresponding Security Profile. Be sure that the setting for Captive Portal is set to webauth in this profile. Then click Configuration > Security > Profile, select the security profile from the list, and then set Security Logging On (Level 10 required). For more information , see the Captive Portal chapter of the System Director Configuration Guide.
Use this page to configure Captive Portal (Level 10 required)
|
Server Port |
Traffic received on this port will direct users to the Captive Portal Login Page. The TCP port number range is 1024 through 65,535 and the default port is 10101. |
| User Authentication Protocol | Name of the protocol used to authenticate the user, or None if none specified |
| Server Lifetime | Lifetime interval of the SSL rekey period. Lifetime is 100 seconds (non-configurable) which is about 1.6 minutes |
| Server IP | IP address of the of the Captive Portal server |
| Certificate | Server Certificate name if one is configured; otherwise, the field is blank |
|
Primary RADIUS Profile Name |
To use an existing Radius server, select a profile from this list. Create or alter these profiles from Configuration > Security > Radius. |
|
Secondary Radius Profile Name |
To use an existing Radius server, select a profile from this list. Create or alter these profiles from Configuration > Security > Radius. |
|
Primary Accounting Radius Server |
To use existing Radius Accounting, select a profile from this list. Create or alter these profiles from Configuration > Security > Radius. |
|
Secondary Accounting Radius Server |
To use existing Radius Accounting, select a profile from this list. Create or alter these lists from Configuration > Security > Radius. |
|
Accounting Interim Interval |
How often Captive Portal should update the Radius server (in seconds). |
|
Captive Portal Session Timeout |
If a client session lasts this long (0-1440 minutes), ask the client to reauthenticate. By default, 0 is set, which is no timeout. |
| Captive Portal Activity Timeout | If a client is idle for this many minutes (0-60), ask the client to reauthenticate. By default, 0 is set, which is no timeout. |
| Captive Portal Authentication Type | Authentication type can be Radius, Local, or Local and Radius. |
Captive Portal is configured after you click OK.
Instead of using the Meru Captive Portal solution, you can use a third-party solution; you cannot use both. Companies such as Bradford, Avenda, and CloudPath all provide Captive Portal solutions that work with System Director 4.1 and later. There are two places that you need to indicate a third-party captive portal solution, in the corresponding Security Profile and in the Captive Portal configuration.
Security Profile Setting
Indicate that a third-party Captive Portal solution will be used in the Security Profile by setting the value for Captive Portal to webauth and setting the value for Captive Portal Authentication Method to external. For complete directions, see Add a Security Profile.
Setting on This Page
Indicate that a third-party Captive Portal solution will be used in the Captive Portal configuration by setting Captive Portal External URL to the URL of the Captive Portal box:
To implement a custom Captive Portal solution, see the Captive Portal chapter of the System Director Configuration Guide.