The customizable pages of a Service Zone are divided into two parts: Login Page Customization and Message Page Customization.
In Login Page Customization, administrators can modify the content within Service Disclaimer, General Login Page, Port Location Mapping Free Login, and Port Location Mapping Paid Access Login.
In Message Page Customization, the Login Success Page, Login Succeeded Page. For On-Demand Users, Login Failed Page, Logout Page, Logout Succeeded Page, Logout Failed Page can be customized.
Please click here to know more details.
In this technical guide, the authentication flow on the controller is illustrated using a flowchart. With this flowchart, readers would be able to understand the order in which authentication methods are presented on the controller, so they could better plan the authentication methods they'd like to leverage as well as better understand how they could troubleshoot if necessary.
Furthermore, as will be seen from the flowchart, a variety of authentication methods are available on the controller for network access control, including web-based, 802.1X, WISPr and MAC authentication. How each authentication method works and where to configure its settings are also explained.
Please click here to know more details.
UAM is also one of the authentication methods supported by the EWS controller, besides other authentication methods such as 802.1X authentication and auto login by the controller based on the MAC addresses and/or IP addresses of the devices used. Furthermore, the EWS controller also supports customization to the behavior of UAM through a UAM filter and provides UAMD log. Please click here to know more.
Normally, when a user moves from an edge AP managed by one Controller to another edge AP managed by another Controller, the user would experience network disconnection and have to re-login. However, with Cross Gateway Roaming, the user can stay logged in to the network and continue to enjoy network access without interruption.
Cross Gateway Roaming adopts a star topology that consists of one Master Node that sits at the center and multiple Slave Nodes that connect to it. One Master Node may connect with up to 15 Slave Nodes. A Controller can be in Master Mode or Slave Mode depending on its Cross Gateway Roaming settings.
This technical guide aims to explain the setup flow of Cross Gateway Roaming on the Controller. Below are two exemplary network deployments that deploy Cross Gateway Roaming so that authenticated users could seamlessly roam within the larger network. Please Click here to know more.
- The Site-to-Site VPN feature on the controller is introduced, and guidance on how to build and configure an exemplary site-to-site VPN is provided through step-by-step explanations. Click here to know more details.
- The Remote VPN feature on the controller is introduced, and guidance on how to setup and configure remote VPNs on the controller as well as on client devices is provided. Click here to know more details.
There are multiple types of logs and reports in the Controller, as described in the following:
a. CAPWAP Log
b. Configuration Change Log
c. Local Monthly Usage
d. Local Web Log
e. Micros Opera Log
f. On-Demand Billing Report
g. RADIUS Server Log
h. SIP Call Usage Log
i. SMS API Log
j. System Log
k. UAMD Log
l. User Events
In this guide, mechanisms of these different MAC address-based access control options are explained and a comparison between them is given. Possible scenarios for these MAC address-based access control options are also illustrated. Moreover, step-by-step configuration guides are provided to facilitate the configuration process. Click here to know more details.
This technical guide should help network administrators to easily setup and configure bandwidth limitation for all users in the network. Click here to know how to setup the User Bandwidth Throttling.
1. Set the Wired Network Discovery VLAN ID to 10. Wired Network Discovery VLAN ID is the management VLAN that AP will using to communicate with AC controller after success managed by AC controller.
(When the value not set to zero, means enabled VLAN classification at ALL AP that using this profile)
2. Modify the VLAN at corresponding VAP that want to enabled (default VLAN is 1)
3. Then apply the profile to take effect the configuration. (Remember need configure corresponding VLAN at the switch first before apply the profile.)
Captive Portal Scenario
Setup Captive Portal
1. Enabled Captive Portal at Global Configuration.
System > Security > Captive Portal> Global Configuration
2. Set Verification Mode as Local at CP Configuration.
System > Security > Captive Portal> CP Configuration
3. Add user at Local User.
System > Security > Captive Portal> Local User
4. Add the VAP to Associated Interface at Interface Association page.
System > Security > Captive Portal> Interface Association