Add your first switch or AP
A network access device (NAD) is any switch, wireless controller, access point, firewall or VPN gateway that asks Airgate whether a user or device may connect. This page lists what every NAD needs, whatever the vendor, and how to add it in Airgate. For vendor-specific commands, see Switches, APs and controllers.
Before you begin
Section titled “Before you begin”- Administrator access to the NAD.
- An Airgate role that can change policy (Tenant Administrator or Network Administrator).
- Decide how the NAD reaches Airgate:
| Path | Use it when |
|---|---|
| RADIUS over UDP to the Airgate appliance or cloud address | The NAD reaches Airgate directly from a fixed address that no other tenant uses. |
RadSec (RADIUS over TLS, TCP 2083) |
The NAD supports RadSec. Recommended for NADs behind NAT or on the internet. |
| Through a site connector | The NAD speaks only UDP RADIUS and sits behind NAT, or you need on-site Active Directory checks. Point the NAD at the connector’s local address. See Sites and site connectors. |
What a NAD needs
Section titled “What a NAD needs”| Setting on the NAD | Value |
|---|---|
| RADIUS authentication server | The Airgate address (or the site connector’s), UDP port 1812 |
| RADIUS accounting server | The same address, UDP port 1813 |
| Shared secret | A long random string. The same value goes into RADIUS shared secret in Airgate. |
| Message-Authenticator | Send it in every Access-Request (protection against BlastRADIUS, CVE-2024-3596). |
| Accounting | Start, stop and interim updates. Airgate uses them for Connected now, device IP addresses and profiling. |
| Dynamic authorization (CoA) | Accept CoA and Disconnect-Request from Airgate on UDP port 3799 (Cisco IOS default is 1700), with the same shared secret. |
| NAS identification | A stable source address for RADIUS (for example a loopback or management interface). The address must match what you enter in Airgate. |
| For 802.1X | 802.1X on the ports or a WPA2/WPA3-Enterprise SSID, with Airgate as the RADIUS server. |
| For MAC authentication | MAB on the ports, or MAC authentication on the SSID, with Airgate as the RADIUS server. |
| For TACACS+ (optional) | Airgate as TACACS+ server, TCP port 49, with a TACACS+ key. |
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 the General tab:
- Name: a name you recognise, such as
sw-floor2-01. - IP address or subnet: the source address of the NAD’s RADIUS packets. A subnet (for example
10.0.10.0/24) covers many APs at once. Prefixes of different tenants may not overlap. - Description: optional.
- Vendor profile: the device platform. It sets Vendor (RADIUS dictionary) and the default CoA port.
- Vendor (RADIUS dictionary): available to rules as
Device:Device-Type. - Site connector: pick the site connector if the NAD sends RADIUS through one.
- Status: enabled. Packets from a disabled device are dropped.
- Name: a name you recognise, such as
- On the RADIUS, CoA & RadSec tab:
- RADIUS shared secret: the secret you set on the NAD. Leave it empty only for RadSec-only devices.
- TACACS+ shared secret: only if the device uses Airgate for administrator logins.
- Require Message-Authenticator in Access-Requests: on. Turn it off only for legacy devices that cannot send it.
- RADIUS CoA / Disconnect (RFC 5176): on if the NAD supports it.
- CoA port:
3799unless the NAD uses another port. - Accept RadSec from this device: on for RadSec. Expected certificate identity (CN): the CN of the NAD’s client certificate. Empty means the CN must be the device ID that Airgate assigns.
- On the Groups & attributes tab (optional): add the device to device groups (for example
Building AorAccess switches) and add custom attributes. Groups let policies and enforcement profiles apply to some devices only. - On the SNMP tab (optional): let Airgate read the device over SNMP for device profiling.
- Select Add device.
Step 2: Configure the NAD
Section titled “Step 2: Configure the NAD”Configure the NAD with the values from What a NAD needs. See Switches, APs and controllers for the exact commands for Cisco, Aruba, Juniper, Meraki, Ruckus, Fortinet and others.
Verify
Section titled “Verify”- Connect a test device, or trigger a RADIUS test from the NAD.
- Go to Monitor › Sign-in log. A record appears with the NAD’s name under Switch / AP. A reject with No access policy handles this sign-in is expected until you write an access policy: it proves that the NAD reaches Airgate.
- Open the device under Network › Switches and APs. Once it starts sending requests, its recent requests show there.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| Nothing in the Sign-in log, and a Network device event under Monitor › Alerts and events | The NAD sends from an address that is not listed, or with the wrong shared secret, or the device is disabled. | Correct the IP address or subnet or the RADIUS shared secret. Use the source-address check on Switches and APs to see which device serves an address. |
| Nothing in the Sign-in log and no event | The packets do not reach Airgate. | Check routing and firewalls for UDP 1812/1813 (or TCP 2083). Use Monitor › Packet capture to see whether packets arrive. |
| Only some devices of a subnet entry get answers | Several NADs share one subnet entry but use different shared secrets. Requests with the wrong secret get no answer. | Give them the same secret, or add them as separate entries. |
| CoA does not work | CoA is off on the NAD or in Airgate, the port differs, or a firewall blocks UDP from Airgate. | Turn on RADIUS CoA / Disconnect (RFC 5176), check the CoA port, and allow dynamic authorization on the NAD. Behind NAT, use a site connector. |
Related
Section titled “Related”© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security