User's Manual

EnRoute500 User’s Guide
TR0149 Rev. C5
97
The ‘splash.url.<intf>.login’ parameter in the ‘sys’ interface, where <intf> is either ‘wlan1’,
‘wlan2’, ‘wlan3’, or ‘wlan4’, sets the URL that a user is redirected to when they attach to the
interface and have not yet been authenticated. This parameter should not be left blank if
splash pages are enabled for the interface since no client would be able to access the network
through the interface if it does not point to a valid URL.
The ‘splash.url.<intf>.success’ parameter in the ‘sys’ interface, where <intf> is either ‘wlan1’,
‘wlan2’, ‘wlan3’, or ‘wlan4’, sets the URL that a user is redirected to when they have
successfully logged in. If this variable is left blank, a default page that indicates login success
will be displayed.
The ‘splash.url.<intf>.fail’ parameter in the ‘sys’ interface, where <intf> is either ‘wlan1’,
‘wlan2’, ‘wlan3’, or ‘wlan4’, sets the URL that a user is redirected to when a login attempt fails.
If this variable is left blank, a default page that indicates login failure will be displayed.
The ‘splash.url.<intf>.error’ parameter in the ‘sys’ interface, where <intf> is either ‘wlan1’,
‘wlan2’, ‘wlan3’, or ‘wlan4’, sets the URL that a user is redirected to when a login error has
occurred. For example, this page would be displayed if a valid authentication server could not
be reached. If this variable is left blank, a default page that indicates an error has occurred will
be displayed.
All of these URLs can be set on the “Splash Pages” sub-tab under the “AAA” tab on the
“System Parameters” page of the web interface (see
Figure 49).
The example below shows how the ‘wlan1’ and ‘wlan2’ interfaces can be used to set to use
different URLs for the login process.
> use sys
sys> set splash.url.wlan1.login=http://server.domain.com/wlan1_login.htm
sys> set splash.url.wlan1.success=http://server.domain.com/wlan1_success.htm
sys> set splash.url.wlan1.fail=http://server.domain.com/wlan1_fail.htm
sys> set splash.url.wlan1.error=http://server.domain.com/wlan1_error.htm
sys> set splash.url.wlan2.login=http://server.domain.com/wlan2_login.htm
sys> set splash.url.wlan2.success=http://server.domain.com/wlan2_success.htm
sys> set splash.url.wlan2.fail=http://server.domain.com/wlan2_fail.htm
sys> set splash.url.wlan2.error=http://server.domain.com/wlan2_error.htm
The login page must contain specific form information as shown in the sample code in Figure
50 and Figure 51. Figure 50 contains the code required for an interface that requires a login
(‘splash.auth.server.enable.wlanN’ is set to ‘yes’). Figure 51 contains code for a login page
that the user just clicks through to unlock network access. The critical lines in Figure 50 are 6,
9, 10, and 12.
The ‘action’ value in line 6 of Figure 50 must point to a server name for which there is a DNS
proxy entry on the local node and the last part of it must be ‘/radius/login.cgi’. The DNS proxy