Technical data

Configuring Meru Captive Portal

There is an additional option for Local Authentication so that when local authentication

for a Captive Portal user fails, Radius authentication is automatically checked; this option

is called Local and Radius. From the Web UI, configure this by clicking Configuration >

Security > Captive Portal > select an SSL Server > Captive Portal Authentication Type

drop-down box (see below).

Figure 27: Local Captive Portal Authentication Has Two Options

The corresponding CLI command ssl-server captive-portal authentication-type config-

ures the controller to use both local and radius authentication.

Controller(config)# ssl-server captive-portal authentication-type ?

local Set Authentication Type to local.

local-radius Set Authentication Type to Local and Radius.

radius Set Authentication Type to radius.

Optionally Configure Pre-Authentication Captive Portal Bypass

Not all users or traffic types need to be authorized and authenticated by Captive

Portal; users of VPN software can pass through the portal without authentication. To

enable this passthrough firewall filter ID, follow these steps:

1. Click Configuration > Security > Profile.

2. Enter the name of the Passthrough Firewall Filter ID.

3. Click Configuration > QoS > System Settings to see the QosRule section of the

Configuration menu (a license for PPF is required to enter the passthrough rules).

4. Add a rule. Remember that rules are stored in the order they are entered and can

not be modified once they are entered.

5. At the bottom of the screen enter the QoS Filter ID.