How to configure 802.1X authentication on Cisco Meraki access points using Cloudi-Fi as the RADIUS provider.
Prerequisites
Before starting, ensure that you have the following prerequisites:
- A Cisco Meraki access point.
- Cloudi-Fi Radius IPs and Secret
- Access to the Cisco Meraki dashboard.
- Knowledge of your network’s IP addressing scheme.
- Enable API access to the Meraki portal and synchronise your Meraki networks with Cloudi-Fi.
- Access to your firewall to allow several ports:
| Source | Destination | Port | Protocol | Action | Comment |
| 802.1x subnet | Cloudi-Fi IPs | 1815 | UDP | Allow | RADIUS traffic |
| 802.1x subnet | Any | 80 | TCP | Allow | HTTP traffic |
| 802.1x subnet | Any | 443 | TCP | Allow | HTTPS traffic |
| 802.1x subnet | Any | 53 | UDP/TCP | Allow | DNS resolution |
| * | * | * | * | Deny | To be adjusted according to your needs |
1. Get Radius information
You will need the Radius information (Server IPs, Secret, Ports) to proceed with the setup.
| Parameter | Description |
| RADIUS IPs | Provided by Cloudi-Fi |
| Ports | UDP 1815 (Authentication) and 1813 (Accounting) |
| Shared Secret | Obtain via the Cloudi-Fi chatbot or Support team |
You can get the Secret by asking in the Chatbot. Cloudi-Fi’s Support team will provide you with the necessary information.
- What shared secret is used for the Radius server for 802.1X for Cisco Meraki? (Please save this confidential information securely, and do not share it publicly).
2. Generate the API Key
- Navigate to the Meraki administration page
- Select "Organization" then "API & Webhooks"
- Click on Generate API Key
- Tick the box to confirm that you saved the key and click on Done
Note: there is a limit of only two API keys per Meraki administrator.
3. Connect your Meraki organization with your Cloudi-Fi tenant
- Navigate to Cloudi-Fi administration UI
- Go to "Configuration" > "Integrations"
- Select "Meraki" from the integration list
If the "Integration" section is missing, ensure the "Integration Menu" is enabled in your Administrator's profile
- Click on "Enable this Integration" to initiate a new Activation.
- Synchronization Mode Selection:
- Currently, only "Automatic synchronization" mode is available.
- Click "Automatic" to proceed.
A manual mode will be introduced in the future for companies opting not to share an API key.
- Configuration Steps:
- Choose the appropriate Meraki Cloud (World or China).
- Paste the API key from the Meraki portal.
- Click "Connect" to initiate the synchronization process.
- Wizard Configuration:
- The wizard will automatically import your Meraki networks.
- Imported networks will appear in Cloudi-Fi Admin UI under "locations".
Note: It could be useful to create multiple activations if you have devices connected to different Meraki Clouds or multiple Meraki Organisations.
4. Define the synchronization settings
- Define the following parameters:
- Activation name
-
Create_locations
- From networks - only network tags will be imported
- From AP tags - only AP tags will be imported
-
Import
- Both MR (access points) and MX (security appliances)
- Only MX
- Only MR
-
Scan
- Everywhere: Automatically adds new Meraki networks to the locations list
- Only some networks / Only some network tags: New networks appear in the integration for selective import
5. Configure your SSID
- Log in to the Cisco Meraki dashboard
- Select the Meraki network you want to enable 802.1X
- Navigate to the “Access Control” tab.
- Configure as follows:
- Give it a name
- Security: Enterprise with my Radius Server
- Splash Page: None (direct access)
6. Configure the Radius server
Click add a server and configure
| Parameter | Description |
| RADIUS IPs | Provided by Cloudi-Fi |
| Ports | UDP 1815 (Authentication) and 1813 (Accounting) |
| Shared Secret | Obtain via the Cloudi-Fi chatbot or Support team |
7. Client IP and VLAN
- While configuring 802.1X, you can assign clients specific IP addresses and VLANs upon successful authentication.
- Scroll to the “Client IP and VLAN” section.
- Choose the appropriate option for assigning IP addresses:
- Meraki AP Assigned (NAT Mode)
- External DHCP server assigned
- Configure VLAN settings (if applicable):
- If you selected “Use VLAN tagging” in the previous step, select the VLAN tag number to assign clients after authentication.
- Ensure that the corresponding VLAN is properly configured on your network infrastructure.
8. Validation
- After completing the configuration:
- Connect a test client to the SSID.
- The client should be prompted for 802.1X credentials.
- Successful authentication should appear in both:
- Meraki Dashboard > Wireless > Event log
- Cloudi-Fi > Users > Authentications
If authentication fails, verify:
- RADIUS IPs and shared secret match on both sides.
- UDP port 1815 is reachable from the access point.
- The Cloudi-Fi RADIUS service is not blocked by your firewall.