Cisco Meraki MR and MS
This page configures Meraki MR access points and MS switches, in the Meraki dashboard, to authenticate against Airgate, accept CoA, and send guests to the Airgate portal as an external splash page.
Before you begin
Section titled “Before you begin”- The addresses the APs and switches send RADIUS from. Meraki devices send RADIUS from their own management IP, so you usually register a subnet, for example
10.0.10.0/24. - The Airgate RADIUS address (
203.0.113.10in the examples) and a shared secret. - If the devices reach Airgate through NAT, register the public NAT address, or use a site connector.
Step 1: Add the Meraki devices in Airgate
Section titled “Step 1: Add the Meraki devices in Airgate”- Go to Network › Switches and APs › Add device.
- Name
branch-mr, IP address or subnet10.0.10.0/24. - Vendor profile: Cisco Meraki MR access point (or Cisco Meraki MS switch for switches). The dictionary becomes
Meraki, the CoA port3799. - On RADIUS, CoA & RadSec: enter the RADIUS shared secret, keep Require Message-Authenticator in Access-Requests on, turn on RADIUS CoA / Disconnect (RFC 5176).
- Select Save.
Step 2: MR access points (802.1X SSID)
Section titled “Step 2: MR access points (802.1X SSID)”In the dashboard, go to Wireless › Access control and select the SSID, for example Corp-WiFi:
| Setting | Value |
|---|---|
| Security | Enterprise with my RADIUS server (WPA2 or WPA3) |
| RADIUS servers | Host 203.0.113.10, port 1812, secret <shared-secret> |
| RADIUS accounting | Enabled, server 203.0.113.10, port 1813, same secret; interim update interval 10 minutes |
| RADIUS CoA support | Enabled |
| RADIUS proxy | Disabled (with the Meraki cloud proxy, requests do not come from your APs) |
| Client IP assignment | Bridge mode, with RADIUS override for the VLAN if Airgate assigns VLANs |
| Group policies | Airespace-ACL-Name or Filter-Id, when Airgate assigns Meraki group policies |
Meraki accepts CoA only from the RADIUS server configured on the SSID. Airgate’s CoA actions for MR are Reauthenticate and Disconnect.
For MAC authentication on an SSID, set Security to MAC-based access control (RADIUS) with the same server.
Step 3: MS switches
Section titled “Step 3: MS switches”Go to Switching › Access policies › Add an access policy:
| Setting | Value |
|---|---|
| Authentication method | my RADIUS server |
| RADIUS servers | 203.0.113.10, port 1812, secret <shared-secret> |
| RADIUS accounting | Enabled, 203.0.113.10, port 1813 |
| RADIUS CoA support | Enabled |
| Host mode | Multi-Auth |
| Access policy type | Hybrid authentication (802.1X, then MAB) |
Assign the policy to the access ports (Switching › Switch ports › Edit › Access policy). Airgate’s CoA actions for MS are Reauthenticate, Disconnect and Bounce port. On models that support URL redirect, the MS access policy’s walled garden and Cisco-AVPair url-redirect provide CWA with the Cisco IOS-XE / C9800 CWA portal handling.
Step 4: Guest SSID with the Airgate splash page (optional)
Section titled “Step 4: Guest SSID with the Airgate splash page (optional)”Meraki MR supports two splash modes with Airgate:
| Meraki splash | Airgate Vendor handling | How the login completes |
|---|---|---|
| Click-through with a custom splash URL | Meraki click-through | The portal redirects to Meraki’s base_grant_url with a grant duration. |
| Sign-on with my RADIUS server with a custom splash URL | Meraki sign-on splash | The portal posts the user name and password to Meraki’s login_url; the AP sends a RADIUS PAP request to Airgate. |
- In Wireless › Access control for
Corp-Guest, set Splash page to one of the modes above and the RADIUS servers to Airgate (sign-on mode). - In Wireless › Splash page, set Custom splash URL to
https://airgate.contoso.com/portal/<tenant>/<portal>. - Add the portal host to the Walled garden (
airgate.contoso.com). - In Airgate, on the portal’s Login & network section, set Vendor handling to the matching Meraki option, Login model to Web login, and Grant duration (Meraki / Mist) (
0= the remaining account lifetime).
Airgate always allows *.network-auth.com as a login host for Meraki.
Verify
Section titled “Verify”- Monitor › Sign-in log shows the request with Switch / AP =
branch-mr. - In the dashboard, Network-wide › Clients shows the client with the VLAN or group policy Airgate sent.
- On Monitor › Connected now, choose Disconnect. The result is
Disconnect-ACK.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| No requests from some APs | Only one AP address is registered | Register the AP subnet, or the NAT address the APs use. |
| No requests at all | RADIUS proxy is on and requests come from the Meraki cloud | Turn the proxy off, or register the proxy source address. |
CoA timeout |
RADIUS CoA support is off, or CoA does not come from the configured RADIUS server address | Turn it on; make sure CoA leaves from the same Airgate address. |
| Splash login fails | Portal host missing from the walled garden | Add it. |