Access Point Instructions for Cisco Meraki
This page explains the configuration of Cisco Meraki wireless access points for external Captive Portal and RADIUS server authentication.
IronWiFi Console Configuration
- Log into the IronWiFi console or register for free
- Create a new network
- After that, create a new captive portal, with vendor Cisco Meraki
Access Point Configuration
Sign-in to the Meraki cloud portal.
- Navigate to Wireless -> Configure -> SSIDs and define a network that we will protect with a Captive Portal with RADIUS authentication. Click edit settings next to Access Control. Configure Access Control with:
- Association requirements - Open (no encryption)
- Splash page - Sign-on with my RADIUS server
RADIUS for splash page
- 1. Host - get this value from the IronWiFi console
- 1. Port - get this value from the IronWiFi console
- 1. Secret - get this value from the IronWiFi console
- 2. Host - get this value from the IronWiFi console
- 2. Port - get this value from the IronWiFi console
- 2. Secret - get this value from the IronWiFi console
- Failover policy - Deny access
- Load balancing policy - Strict priority order
- Network access control - Disabled
- Assign group policies by device type - Disabled
- Walled Garden - Walled Garden is enabled
- Walled Garden Ranges - 107.178.250.42/32
RADIUS accounting - If you don't see RADIUS Accounting servers, contact Meraki support to enable this feature in your account.
- RADIUS accounting - enabled
- 1. Host - get this value from the IronWiFi console
- 1. Port - get this value from the IronWiFi console
- 1. Secret - get this value from the IronWiFi console
- 2. Host -get this value from the IronWiFi console
- 2. Port -get this value from the IronWiFi console
- 2. Secret -get this value from the IronWiFi console
- Data-Carrier Detect - enabled
- Navigate to Wireless -> Configure -> Splash page and configure:
- Custom Splash URL -get this value from the IronWiFi console
If data-carrier detect is enabled, sessions will be revoked and accounted for whenever a client disassociates from a network. To allow clients to reassociate to the network without re-authorization, do not enable data-carrier detect.
If you have devices that don't have support for two way authentication like printers, Smart TV, etc., you can white-list these devices directly in the Meraki Console -