Connect switches, APs and controllers
This section shows how to point your switches, wireless controllers and access points (network access devices, NADs) at Airgate for 802.1X, MAC authentication (MAB), Change of Authorization (CoA) and the guest captive portal. Start here for the settings every device needs, then open the page for your vendor.
How a device talks to Airgate
Section titled “How a device talks to Airgate” Client ──EAP / MAC──► Switch / AP / controller ──RADIUS (UDP 1812/1813)──► Airgate │ ◄──────────────── CoA / Disconnect (UDP 3799) ──┘ │ └── or RadSec (RADIUS over TLS, TCP 2083) ──────► Airgate
Devices on private networks: Switch / AP ──RADIUS──► Site connector (LAN) ──RadSec or HTTPS──► Airgate ◄──CoA────┘Airgate identifies the device, and through it your tenant, by the source address of the RADIUS packet (or, for RadSec, by the device’s client certificate). A request from an address that is not registered under Network › Switches and APs, or from a disabled device, gets no answer.
What every network device needs
Section titled “What every network device needs”| Setting | Value | Notes |
|---|---|---|
| RADIUS authentication server | Airgate RADIUS address, UDP 1812 |
203.0.113.10 in the examples in this section. Use the site connector’s LAN address instead when the device sits behind a site connector. |
| RADIUS accounting server | Same address, UDP 1813 |
Accounting feeds Monitor › Connected now, session-based CoA and device IP addresses. Turn it on. |
| Shared secret | The RADIUS shared secret you enter for the device in Airgate | Use a long random secret, different per site or device. |
| Interim accounting updates | On, every 5 to 15 minutes | Sessions without any accounting update are closed after Close stale sessions after on Settings › General (if set). Interim updates also report the client IP address. |
| Message-Authenticator | Sent in every Access-Request | Protection against BlastRADIUS (CVE-2024-3596). Airgate requires it by default and drops Access-Requests without it. All 802.1X (EAP) requests carry it; check that MAB and PAP requests do too. |
| NAS-IP-Address / source interface | A fixed management address that matches the device entry in Airgate | Pin the RADIUS source interface so packets do not leave from a changing address. |
| Dynamic authorization (CoA / Disconnect, RFC 5176) | Accept from Airgate on UDP 3799 (Cisco IOS default 1700), same shared secret |
Lets Airgate and administrators re-authenticate, bounce or disconnect a session. When a site connector serves the device, CoA comes from the connector’s LAN address. |
| RadSec (optional) | TCP 2083, client certificate |
For devices behind NAT or on shared addresses. See RadSec. |
| Calling-Station-Id | The client MAC address | Airgate accepts the usual MAC formats (aa:bb:cc:dd:ee:ff, AA-BB-CC-DD-EE-FF, aabbccddeeff, aabb.ccdd.eeff). |
Step 1: Add the device in Airgate
Section titled “Step 1: Add the device in Airgate”- Go to Network › Switches and APs and select Add device.
- On General, enter:
- Name, for example
core-sw1. - IP address or subnet: the source address of the device’s RADIUS packets, for example
10.0.0.2. For many access points that each send RADIUS themselves, enter their subnet, for example10.0.10.0/24. - Vendor profile: the platform, for example Cisco IOS-XE switch (Catalyst 9k, IBNS). The profile sets the RADIUS dictionary, the default CoA port, the CoA packet format and the captive-portal model Airgate uses for this device.
- Vendor (RADIUS dictionary): filled in by the profile. It decides which vendor-specific attributes (VSAs) the device is sent and how its requests are read.
- Site connector: only if the device reaches Airgate through a connector.
- Name, for example
- On RADIUS, CoA & RadSec, enter:
- RADIUS shared secret.
- Require Message-Authenticator in Access-Requests: leave it on unless the device cannot send it.
- RADIUS CoA / Disconnect (RFC 5176): on, and the CoA port the device listens on.
- TACACS+ shared secret: only if administrators log in to the device through Airgate (see Switch administration with TACACS+).
- Optional: on Groups & attributes, add the device to device groups (for example by site or by type) so access policies and enforcement profiles can target it.
- Select Save.
Vendor profiles and what Airgate uses for each:
| Vendor profile | Dictionary | Default CoA port | CoA actions | Guest portal model |
|---|---|---|---|---|
| Aruba AOS 8 Mobility Controller / Conductor | Aruba | 3799 | Disconnect, change attributes, bounce | Web login |
| Aruba Instant / AOS 10 APs (Central) | Aruba | 3799 | Disconnect, change attributes | Web login |
| Aruba AOS-CX switch | Aruba | 3799 | Disconnect, bounce, change attributes | MAC caching + CoA |
| ArubaOS-Switch / HPE ProCurve | HP | 3799 | Disconnect, bounce, change attributes | MAC caching + CoA |
| Cisco IOS-XE switch (Catalyst 9k, IBNS) | Cisco | 1700 | Reauthenticate, disconnect, bounce, disable port | MAC caching + CoA |
| Cisco Catalyst 9800 WLC / AireOS | Cisco | 1700 | Reauthenticate, disconnect | MAC caching + CoA (CWA) or web login |
| Cisco Meraki MR access point | Meraki | 3799 | Reauthenticate, disconnect | Web login (splash) |
| Cisco Meraki MS switch | Meraki | 3799 | Reauthenticate, disconnect, bounce | MAC caching + CoA |
| Ruckus SmartZone / RUCKUS One / Unleashed / ZoneDirector | Ruckus | 3799 | Disconnect, change attributes | Web login |
| FortiGate (FortiAP wireless, captive portal, user groups) | Fortinet | 3799 | Disconnect | Web login |
| FortiSwitch (standalone or FortiLink) | Fortinet | 3799 | Reauthenticate, bounce, disable port, disconnect, change attributes | None |
| Juniper Mist access point | Juniper | 3799 | Reauthenticate, disconnect | Mist authorize URL |
| Juniper EX switch (Junos dot1x) | Juniper | 3799 | Disconnect, bounce, change attributes | MAC caching + CoA |
| Arista EOS (802.1X / MAC-based authentication) | Arista | 3799 | Disconnect, bounce | MAC caching + CoA |
| Arista CloudVision CUE Wi-Fi | Arista | 3799 | Disconnect | Vendor portal |
| Extreme EXOS / Universal switch / Campus Controller | Extreme | 3799 | Disconnect, change attributes | MAC caching + CoA |
| ExtremeCloud IQ (Aerohive) access point | Aerohive | 3799 | Disconnect, change attributes | Web login (grant URL) |
| Ubiquiti UniFi | IETF | none | none (no RADIUS CoA) | Not supported |
| Generic IETF (RFC 3580 / RFC 5176) | IETF | 3799 | Disconnect, change attributes | None |
When a CoA kind the platform has no native packet for is requested, Airgate falls back to a Disconnect.
Per-device CoA overrides
Section titled “Per-device CoA overrides”Three optional custom attributes on Groups & attributes tune CoA for one device:
| Attribute | Value | Use |
|---|---|---|
CoA-Address |
An IP address | Send CoA to this address instead of the session’s NAS address, for example the Aruba Instant virtual controller IP. |
CoA-Template |
A vendor profile, for example cisco-iosxe-switch |
Use another platform’s CoA packet format than the device’s vendor profile. |
CoA-MAC-Format |
colon, hyphen, upper-hyphen, upper-colon, nodelim, upper-nodelim or dot |
Calling-Station-Id format in CoA packets when Airgate does not have the device’s own spelling. |
Step 2: Configure the device
Section titled “Step 2: Configure the device”Open the page for your platform:
| Vendor | Page |
|---|---|
| Aruba Instant On, Instant APs and AOS 10 | Aruba Instant and IAP |
| Aruba CX switches | Aruba CX |
| Aruba Mobility Controllers (AOS 8) | Aruba Mobility Controller |
| Cisco Catalyst switches (IOS-XE) | Cisco Catalyst |
| Cisco Catalyst 9800 wireless controllers | Cisco WLC 9800 |
| Cisco Meraki MR and MS | Cisco Meraki |
| Juniper EX and Mist | Juniper EX and Mist |
| FortiGate, FortiSwitch, FortiAP | Fortinet |
| Ruckus SmartZone, RUCKUS One, ICX | Ruckus |
| Ubiquiti UniFi | Ubiquiti UniFi |
| Edgecore | Edgecore |
| Anything else (standard RADIUS) | Other vendors |
RadSec
Section titled “RadSec”RadSec (RADIUS over TLS, RFC 6614) carries RADIUS over TCP 2083 with mutual certificate authentication. Use it when the device’s address is translated (NAT), shared with other customers, or when RADIUS must cross the internet without a site connector.
- On the device entry, turn on Accept RadSec from this device. You can leave RADIUS shared secret empty for a RadSec-only device.
- Give the device a client certificate issued by your tenant’s NAD CA (RadSec) (see Certificate authorities), or by your own CA imported under Certificates › Trusted CAs and trusted for Network devices (RadSec).
- The certificate’s common name must equal the device ID, or the value in Expected certificate identity (CN) on the device entry.
- On the device, configure a RadSec server
203.0.113.10port2083with that client certificate, and trust the Airgate RadSec server certificate (signed by the platform root, see Certificates and trust).
Verify
Section titled “Verify”- Connect a test client, then open Monitor › Sign-in log. You should see the request with your device under Switch / AP, the rule that matched and the attributes sent.
- On Network › Switches and APs, select the device. Overview shows whether its address is accepted as a RADIUS client; the Activity tab shows its requests and failures in the last 24 hours.
- Open Monitor › Connected now, select the session and choose Reauthenticate. The result should be
CoA-ACK.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| Nothing in the Sign-in log; Monitor › Alerts and events shows the address as an unknown network device | The source address is not registered | Add the device, or correct IP address or subnet to the real source address (check the RADIUS source interface). |
| Nothing in the Sign-in log; the alert says the shared secret is wrong | The secret differs between the device and Airgate | Re-enter the same secret on both sides. |
| Nothing in the Sign-in log for MAB or PAP only | The device sends no Message-Authenticator and Require Message-Authenticator in Access-Requests is on | Update the device software or enable Message-Authenticator on it. Turn the requirement off only for legacy devices. |
| Requests from a device behind a site connector are refused | The device is assigned to a connector but sends to the cloud address | Point the device at the connector’s LAN address. |
CoA result timeout |
Wrong CoA port, CoA not enabled on the device, or a firewall drops UDP 3799 | Match CoA port to the device, enable dynamic authorization for the Airgate address, open the port. |
CoA result CoA-NAK / Disconnect-NAK |
The device does not know the session, or rejects the packet (time window, attributes) | Check that accounting is on and the device clock is in sync; check the vendor page for its CoA requirements. |
| Users land in the wrong VLAN or role | The enforcement profile sends attributes in another vendor’s dictionary | Use an enforcement profile template for this vendor on Access › Enforcement profiles. |