Other vendors (standard RADIUS)
Any network device that speaks standard RADIUS can authenticate users and devices against Airgate. This page lists the standard attributes Airgate uses, how to register a device without a dedicated page, and the key facts for the other platforms Airgate has vendor profiles for.
Before you begin
Section titled “Before you begin”- The device’s RADIUS source address, for example
10.0.0.2. - The Airgate RADIUS address (
203.0.113.10in the examples) and a shared secret. - See What every network device needs.
Step 1: Add the device in Airgate
Section titled “Step 1: Add the device in Airgate”- Go to Network › Switches and APs › Add device.
- Enter Name and IP address or subnet.
- Vendor profile: the matching profile from the table below, or Generic IETF (RFC 3580 / RFC 5176).
- Vendor (RADIUS dictionary): when you use the generic profile, pick the device’s vendor under All RADIUS dictionaries if Airgate should read and send its vendor-specific attributes; otherwise keep
IETF. - On RADIUS, CoA & RadSec: RADIUS shared secret, Require Message-Authenticator in Access-Requests (on unless the device cannot send it), RADIUS CoA / Disconnect (RFC 5176) and CoA port if the device supports RFC 5176.
- Select Save.
Step 2: Configure the device
Section titled “Step 2: Configure the device”Configure on the device:
| Setting | Value |
|---|---|
| RADIUS authentication | 203.0.113.10, UDP 1812, shared secret |
| RADIUS accounting | 203.0.113.10, UDP 1813, start-stop with interim updates every 5 to 15 minutes |
| 802.1X | Port-based or SSID-based, with Airgate as the server |
| MAC authentication | User-Name = the MAC, and Calling-Station-Id = the MAC |
| Dynamic authorization (RFC 5176) | Client 203.0.113.10, UDP 3799, same secret |
| NAS-IP-Address | The registered address |
Standard attributes Airgate sends
Section titled “Standard attributes Airgate sends”| Purpose | Attributes | Enforcement profile template |
|---|---|---|
| VLAN assignment (RFC 3580) | Tunnel-Type = VLAN (13), Tunnel-Medium-Type = IEEE-802 (6), Tunnel-Private-Group-Id = <vlan> |
VLAN Enforcement |
| Named ACL or policy | Filter-Id = <name> |
Filter-Id Enforcement |
| Re-authentication interval | Session-Timeout, Termination-Action |
RADIUS Based Enforcement (add the rows) |
With the generic profile, Airgate’s CoA actions are Disconnect (Disconnect-Request) and changing attributes (CoA-Request with the new attributes). Reauthenticate and bounce, which need vendor-specific attributes, fall back to a Disconnect.
Other platforms with an Airgate vendor profile
Section titled “Other platforms with an Airgate vendor profile”| Platform | Vendor profile | Notes from the profile |
|---|---|---|
| HPE ArubaOS-Switch / ProCurve | ArubaOS-Switch / HPE ProCurve (dictionary HP) |
Roles with HP-User-Role; VLANs with RFC 3580 or Egress-VLANID / Egress-VLAN-Name. CoA on 3799 (radius-server host 203.0.113.10 dyn-authorization plus a time window); CoA without Event-Timestamp is rejected, so keep NTP in sync. Bounce uses HP-Port-Bounce-Host. Guests: MAC caching + CoA with a SPLASH role (HP-User-Role + HP-Captive-Portal-URL) and Vendor handling Aruba switch (AOS-CX / AOS-S). |
| Arista EOS switches | Arista EOS (802.1X / MAC-based authentication) (dictionary Arista) |
CoA on 3799: Disconnect and bounce (Arista-PortFlap). Guests: Arista-AVPair url-redirect-acl and url-redirect (EOS 4.29.1F or later), Vendor handling Arista EOS, MAC caching + CoA. Do not use radius proxy … dynamic-authorization (CVE-2026-73449); set no dynamic-authorization under the RADIUS proxy. Dynamic authorization over TLS uses port 2083. |
| Arista CloudVision CUE Wi-Fi | Arista CloudVision CUE Wi-Fi | CoA: Disconnect. Captive portal is the vendor’s own. |
| Extreme EXOS / Universal switches / Campus Controller | Extreme EXOS / Universal switch / Campus Controller (dictionary Extreme) |
VLANs with RFC 3580 or Extreme-Netlogin-Vlan; policy roles as Filter-Id = Enterasys:version=1:policy=<role>. Guests: netlogin redirect with mac and dest, Vendor handling Extreme EXOS, MAC caching + CoA. |
| ExtremeCloud IQ (Aerohive) APs | ExtremeCloud IQ (Aerohive) access point (dictionary Aerohive) |
CoA: Disconnect and changing attributes. Guests: external captive portal; Airgate redirects to the AP’s grant URL (Vendor handling ExtremeCloud IQ). |
Guest portal with other devices
Section titled “Guest portal with other devices”If the device redirects guests to an external portal and accepts a login form post, choose Vendor handling Generic on the portal’s Login & network section, and fill in Login URL (it may use {nad_ip} and {login_host}), Method, Username field, Password field and Extra form fields (values may use {original_url}, {mac} and {ip}). Airgate reads the usual redirect parameter names (mac, client_mac, ip, client_ip, ssid, url, redirect, login_url, nas_ip and others).
Verify
Section titled “Verify”- Monitor › Sign-in log shows the request with the device under Switch / AP.
- If you enabled CoA, choose Disconnect on the session in Monitor › Connected now. The result is
Disconnect-ACK.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| No request in the Sign-in log | Address or shared secret mismatch | Check Monitor › Alerts and events for an unknown device or wrong secret. |
| VSAs not applied | The device entry uses IETF while the profile sends vendor attributes |
Set Vendor (RADIUS dictionary) to the device’s vendor. |
CoA timeout |
The device has no RFC 5176 support, or another port | Turn CoA off for the device, or set the right CoA port. |