Information required for FansWiFi Manager
Base Radio Mac of the APs (It may not the same as the Mac Address of the AP on the label)
Tested Cisco WLC Firmware Version
8.0.121.0, 8.2
Recommended Version: 8.2 or above
Radius Debugging Tools for Troubleshooting is only available for firmware version 8.2 or above. See Troubleshooting step below.)
FansWiFi Server / Controller Communication
The table below listed the ports that must be opened on the network firewall to ensure that the Cisco WLC, FansWiFi servers(including RADIUS server) can communicate with each other successfully.
Port Number | Protocol | Source | Destination | Traffic Direction | Purpose | Required by Login Method |
1812 / 1813 | UDP & TCP | Controller | FansWiFi RADIUS Server (103.6.85.240) | outbound | AAA Authentication and Accounting | All |
1700 / 3799 | UDP & TCP | FansWiFi Radius Server IP (103.6.85.240) | Controller | inbound (port forwarding may needed by your firewall / router. Depends on your network setup.) | RADIUS CoA Messages | WeChat Login / Video Login |
Network Diagram
Communication between WLAN Controller and FansWiFi Server Cluster on Cloud
Setting on Cisco Wireless Lan Controller (WLC)
Step 1: Configure the WLC
Access the WLC by opening a Web Browser:
Step 2: Configuration: Authentication Servers
Click Security Tab on the top menu
Click AAA > Radius > Authentication from the left menu
Click New... with below Setting
IP Address: 103.6.85.240
Shared Secret: social123
Confirm Secret: social123
Port: 1812
Network User: (tick) Enable
Management: (untick) Disable
Click Apply to save the configuration
Step 3: Configuration: Accounting Servers
Accounting
Click "AAA > Radius > Accounting" from the left menu
Click "New..." with below Setting
IP Address: 103.6.85.240
Shared Secret: social123
Confirm Secret: social123
Port: 1813
Network User: (tick) Enable
Click "Apply" to save the configuration
Step 4: Configuration: Web Auth
Click "Web Auth > Web Login Page" from the left menu
Configure the below setting
Web Authentication Type: External (Redirect to external server)
Redirect URL after login: https://connect-p.fanswifi.com/auth?res=success&id=cisco
External Webauth URL: https://connect-p.fanswifi.com/auth
Click "Apply" to save the configuration
Please make sure you enter “https” in the URL instead of “http”
Step 5: Configuration: Access Control List
Click "Security" on the top menu, then click "Access Control List > Access Control Lists" on the left menu
(Optional) if your setting is using FlexConnect Mode, please click "Access Control Lists > FlexConnect ACLs" instead
Click "New" on the Access Control Lists page to add new list
Enter "FansWiFi" as the "Access Control List Name"
Choose "IPv4" as "ACL Type"
Click "Apply" to save the configuration
Select "FansWiFi" on the Access Control Lists page to edit the list we just created
Click "Add New Rule" on the top right corner
Configure the Access Control List according to below table
Aim: Allow WiFi user accessing FansWiFi Captive Portal Server (52.220.206.125, 52.220.226.90) and Social Media (e.g. Facebook) to complete Social Login process
Sequence | Source | Destination | IP Address | Netmask | Protocol | Source | Destination | Action |
1 | Any | Any |
|
| TCP | HTTPS | Any | Permit |
2 | Any | Any |
|
| TCP | Any | HTTPS | Permit |
3 | IP Address | Any | 52.220.206.125 | 255.255.255.255 | Any | Any | Any | Permit |
4 | Any | IP Address | 52.220.206.125 | 255.255.255.255 | Any | Any | Any | Permit |
5 | IP Address | Any | 52.220.226.90 | 255.255.255.255 | Any | Any | Any | Permit |
6 | Any | IP Address | 52.220.226.90 | 255.255.255.255 | Any | Any | Any | Permit |
Step 6: Disable WebAuth SecureWeb in the HTTP-HTTPS setting
Select “Management" from the above menu
Click “HTTP-HTTPS" on the left side menu
Disable the "WebAuth SecureWeb" option
Click Apply
Click Save Configuration
Reboot the Controller
Controller must be rebooted for the WebAuth SecureWeb configuration change to take effect
Step 7: Create WLAN and SSID for customer access
Select “WLANs” from the top menu
Click “Create New” and give it a name.
Click on the newly created Wlan and it will open the configuration menu below.
Profile Name: FansWiFi
SSID: FansWiFi
Status: Enabled
NAS-ID: socialnas
Click Security tab.
Click Layer 2
Click Layer 3
Click AAA server tab
Click "Advanced"
Step 8: Save Configuration
Make sure to always save configurations after editing the settings in the right hand corner.
Step 9: Configure Cisco Controller IP Address to FansWiFi Admin Panel for Radius CoA
*** Please send this information to your FansWiFi account manager
(Required for WeChat WiFi, you may skip this step if there is no WeChat WiFi Enabled)
FansWiFi Admin Panel (Setting > Venue Setting)
Send below information to FansWiFi
Public IP Addresses / Domain Name of Cisco Controller
Radius CoA Port: 1700 / 3799
Exceptional Case: ZoneDirector behinds Router / Firewall
If the ZoneDirector is behind Router / Firewall, it is not directly accessible via FansWiFi Radius Server via Internet. In this case, you need to configure port forwarding on your Router / Firewall to forward the port to the ZoneDirector
Please see below example:
Assume the Public IP of the Router is 1.1.1.1 in this example
1. Configure Port Forwarding to forward Router’s Port 1700 and 3799 to WiFi Controller's CoA Port (Default: 1700 and 3799)
Inbound port: 1700 / 3799
(You can replace any port you want in your setup)
Destination IP: 192.168.1.100 (ZoneDirector’s IP in your network)
Destination Port: 1700 / 3799
2. Send below information to FansWiFi
Public IP Addresses of Router: 1.1.1.1 or Domain Name (URL)
Radius CoA Port: 3799 (You can replace any port you want in your setup)
Setting in FansWiFi Admin Panel
Step 10: Add AP to FansWiFi Admin Panel
Log in to FansWiFi Admin Panel
Click Settings” -> Hotspots -> Add Hotspot
venue: Select the venue of where your Access Point locates
Hotspot Name: Name each Access Point to make it identifiable
AP Type: Select “Cisco WLC”
Mac Address: Input unique Base Radio MAC of each Access Point in your venue (Not controller) (Base Radio MAC may not be the same as the Mac Address of the AP printed on the label. Please check the Base Radio MAC via Monitor -> Access Points on the WLC WebUI)
Click Save
Step 11: Troubleshooting
Test AAA RADIUS Interactions for WLAN Authentication
Requirement: Cisco WLC Firmware Version 8.2 or above
Execute below commands to query our Radius server using our test account (username: test, password: testinggogogo)
(Cisco Controller) > test aaa radius username test password testinggogogo
(Cisco Controller) > test aaa show radius
If the connection is success, you should see message like below:
Radius Test Request
Wlan-id........................................ 7
ApGroup Name................................... default-group
Server Index................................... 2
Radius Test Response
Radius Server Retry Status
------------- ----- ------
103.6.85.240 1 Success
Authentication Response:
Result Code: Success
Attributes Values
---------- ------
User-Name user1
Class CACS:rs-acs5-6-0-22/230677882/20313
Session-Timeout 0x0000001e (30)
Termination-Action 0x00000000 (0)
Tunnel-Type 0x0000000d (13)
Tunnel-Medium-Type 0x00000006 (6)
Tunnel-Group-Id 0x00000051 (81)
If the connection do not success, you should see message like below:
Radius Test Request
Wlan-id........................................ 7
ApGroup Name................................... default-group
Server Index................................... 3
Radius Test Response
Radius Server Retry Status
------------- ----- ------
172.20.227.72 6 No response received from server
Authentication Response:
Result Code: No response received from server
No AVPs in Response
You can also enable the debug message for more details by using below command
(Cisco Controller) > debug aaa all enable
Reference:
Cisco Wireless Controller Configuration Guide, Release 8.2
Chapter: Debugging on Cisco Wireless Controllers