User's Manual

Chapter 18: Integration with Enterprise Equipment
TR0153 Rev. E1 136
Web GUI
All of the splash page-related 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 59).
18.1.3 Sample HTML Code for Splash Pages
The login HTML page must contain specific form information as shown in the sample code in
Figure 60 and Figure 61. Figure 60 contains the code required for an interface that requires a
login. Figure 61 contains code for a login page that the user just clicks through to unlock
network access.
The critical lines in Figure 60 are 6, 12, 15, and 19. The ‘action’ value in line 6 of Figure 60
must point to a server name for which there is a DNS proxy entry on the local mesh device and
the last part of it must be ‘/radius/login.cgi’. The DNS proxy entry, which will be different for
each mesh device in the network, must be mapped to one of the EnRoute500’s IP addresses
(see section 8.8 for more information on how to set the DNS proxy configuration).
The example below shows how to configure the DNS proxy assuming the login page redirects
to the host ‘redirect.domain.com’ and the IP address of the wlan1 interface is 10.1.2.1.
> use sys
sys> set dnsproxy.enable=yes
sys> set dnsproxy.hosts=”dns.proxy.name.here=10.1.2.1”
The DNS proxy setting is used in conjunction with the splash pages to ensure that a
common login URL can be used on all mesh devices. The DNS proxy entry directs
the results of the login process to the right location – that is, the EnRoute500 that the
client device is connected to.
The login page must also contain the ‘input’ fields on lines 12, 15, and 19. These are used to
allow a user logging in to provide their username and password, and to submit them. The
names of these input fields, ‘username’, ‘password’, and ‘login’, must not be changed.