Tranzeo Wireless Technologies Inc GNVPZ1NT3 Manuale Utente
Chapter 18: Integration with Enterprise Equipment
TR0153 Rev. E1
133
18 Integration with Enterprise Equipment
The EnRoute500 supports authentication, accounting, and monitoring services that easily
integrate with enterprise equipment. In this section the following topics are described:
• Splash pages
• Backhaul health monitoring
• Layer 2 client emulation
integrate with enterprise equipment. In this section the following topics are described:
• Splash pages
• Backhaul health monitoring
• Layer 2 client emulation
18.1 Configuring Splash Pages
The EnRoute500 supports splash pages, which can be used to restrict access to the mesh
network and provide information to users that connect to the mesh. When a user connects
through a client access interface to an EnRoute500 with splash page support enabled, the
splash page for the appropriate interface will be displayed and the user will be restricted from
accessing other destinations on the Internet until they have logged in. The splash page can
require the user to enter logon credentials or simply click a button to complete the login
process.
To use splash pages, a number of URLs for login, successful login, and failed login must be
specified. A RADIUS server that provides authentication services may also need to be
specified.
network and provide information to users that connect to the mesh. When a user connects
through a client access interface to an EnRoute500 with splash page support enabled, the
splash page for the appropriate interface will be displayed and the user will be restricted from
accessing other destinations on the Internet until they have logged in. The splash page can
require the user to enter logon credentials or simply click a button to complete the login
process.
To use splash pages, a number of URLs for login, successful login, and failed login must be
specified. A RADIUS server that provides authentication services may also need to be
specified.
18.1.1
Enabling Splash Pages
The enabling of splash pages can be controlled on a per-interface basis. Two splash page
mode are supported – one which requires client device users to login in to gain access to the
network and another which requires them to simply click on a button on the web page to
proceed.
mode are supported – one which requires client device users to login in to gain access to the
network and another which requires them to simply click on a button on the web page to
proceed.
CLI
Enable or disable splash pages with the ‘splash.enable.wlanN’ parameters in the ‘sys’
interface. For a splash page to be displayed on an interface, the appropriate parameter must
be set to ‘yes’. The example below illustrates how to set the ‘splash.enable.wlan1’ parameter
in the ‘sys’ interface to enable splash pages for the wlan1 interface.
interface. For a splash page to be displayed on an interface, the appropriate parameter must
be set to ‘yes’. The example below illustrates how to set the ‘splash.enable.wlan1’ parameter
in the ‘sys’ interface to enable splash pages for the wlan1 interface.
> use sys
sys> set splash.enable.wlan1=yes
sys> set splash.enable.wlan1=yes
Use the ‘splash.auth.server.wlanN.enable’ parameters in the ‘sys’ interface to select whether a
user is required to provide login credentials for a particular interface. The example below