Skip to content

How Airgate works

This page follows one sign-in through Airgate, from the moment a device connects to a switch port or Wi-Fi network to the moment the switch or access point applies the result. Read it before you design policies, so you know which facts Airgate has at each step.

Component Role
Network access device (NAD) A switch, wireless controller, access point, firewall or VPN gateway. It asks Airgate whether a user or device may connect (RADIUS), and applies the answer.
RADIUS server Airgate’s RADIUS front end (FreeRADIUS 3.2). It terminates RADIUS and RadSec, runs the EAP conversations (the TLS tunnels of PEAP and EAP-TTLS, the EAP-TLS handshake) and checks passwords. It makes no decisions itself.
Airgate service Airgate’s control plane (nacd). It identifies the tenant and the NAD, picks the access policy, looks up the account in your directories, gathers device facts, evaluates the rules and returns the reply. It also runs the TACACS+ server, the console and API, the portals, the certificate authorities, CoA, profiling and the integrations.
Database PostgreSQL holds every tenant’s configuration, devices, sessions and logs.
Site connector (optional) A small Airgate program at a site. It relays local RADIUS, TACACS+ and DHCP to Airgate and delivers CoA back to the NADs, over outbound connections only.
device ──EAP / MAC──▶ switch or AP ──RADIUS (UDP 1812) or RadSec (TCP 2083)──▶ Airgate RADIUS
▲ │
│ ▼
│ Airgate service (nacd)
│ 1 tenant and NAD 2 access policy (service)
│ 3 method allowed? 4 account lookup (directories)
│ 5 device facts 6 rules → enforcement profiles
│ │
└────────── Access-Accept + VLAN / role / ACL ◀─────────┘
or Access-Reject
later: CoA / Disconnect (UDP 3799) ◀── Airgate, when something changes
  1. The device connects. A laptop starts 802.1X on a port or joins a WPA2/WPA3-Enterprise SSID, or a printer is plugged into a port that does MAC authentication (MAB). The switch or AP sends a RADIUS Access-Request to Airgate. It sends it over UDP 1812, over RadSec (RADIUS over TLS, TCP 2083), or to a site connector on the local network, which forwards it.
  2. Airgate identifies the NAD and the tenant. The request’s source address must match a device under Network › Switches and APs (an address or a subnet), and the shared secret must match. A RadSec connection is identified by its client certificate. The NAD belongs to exactly one tenant. Requests from unknown addresses, or with a wrong shared secret, get no answer and are reported under Monitor › Alerts and events.
  3. Airgate picks the access policy. Access policies are checked from the top. The first enabled policy whose conditions match (for example the Wi-Fi network, the connection type, the device group of the switch) handles the sign-in. If none matches, the sign-in is refused with No service matched.
  4. Airgate checks the sign-in method. The policy lists the methods it allows (EAP-TLS, PEAP, EAP-TTLS, PAP, CHAP, MS-CHAP, MAC authentication). Anything else is refused with Authentication method not allowed.
  5. The credentials are verified.
    • EAP-TLS: the device presents a client certificate. Airgate checks that it chains to a CA the tenant trusts and is not revoked or expired, then takes the user name from the certificate.
    • PEAP and EAP-TTLS: Airgate builds a TLS tunnel with its RADIUS server certificate. Inside it, the user’s password is checked against the directories the policy lists, in order (Check accounts in).
    • PAP, CHAP, MS-CHAP: the password is checked against the same directories.
    • MAC authentication: the MAC address is looked up in Devices.
  6. Airgate gathers context. For the account: its groups and attributes from the directories. For the device: its record under Devices (status, device type, owner), the compliance facts synced from Intune, CrowdStrike or SentinelOne, and the Intune device ID from its certificate. For the connection: the SSID, the NAD, its device groups, the time of day. All of this is available to rules as attributes, such as Authorization:<directory>:Groups, Endpoint:Intune Compliance State or Connection:SSID.
  7. The rules decide. Inside the policy, rules are checked from the top and the first rule whose conditions are all true wins. Its action (allow with a VLAN, role, ACL, security group tag and session timeout, allow with an enforcement profile, or deny) becomes the answer. If no rule matches, the policy’s default applies (deny unless you set it to allow).
  8. The NAD applies the result. Airgate sends an Access-Accept with the reply attributes, or an Access-Reject. The switch or AP puts the device in the VLAN or role, applies the ACL, and starts the session.
  9. Accounting keeps the session up to date. The NAD sends RADIUS accounting (UDP 1813): start, interim updates and stop. Airgate uses it for Monitor › Connected now, refreshes the device’s IP address and last-seen time, and feeds the device profiler.
  10. Change of Authorization, when something changes. If the right answer for a connected device changes, Airgate sends a CoA or Disconnect-Request to the NAD (UDP 3799 by default). The device re-authenticates and gets the new result. See Change of Authorization.

Every request, accepted or refused, is written to Monitor › Sign-in log with the policy and rule that decided, the attributes Airgate computed, the full trace and the reply.

Administrators who log in to a switch, router or firewall are checked over TACACS+ (TCP 49). The device is identified by its address and its TACACS+ shared secret. Airgate checks the user against the local users and the directories you select, then the rules on Access › Access policies › Switch and router logins decide the privilege level and which commands are allowed. Logins and commands are recorded under Monitor › Admin login log.

Airowire runs Airgate. Your NADs reach it in one of three ways:

Path When to use it
RadSec (TCP 2083, mutual TLS) The NAD supports RadSec. Traffic is encrypted, and the NAD is identified by its certificate, so it can sit behind NAT.
Site connector The NAD speaks only UDP RADIUS, sits behind NAT, or must reach on-premises Active Directory for PEAP-MSCHAPv2. The connector forwards everything over outbound connections.
RADIUS over UDP from a fixed public address Only for NADs with a dedicated public address. The address identifies the NAD, so it must not be shared with another tenant.

The whole of Airgate (database, Airgate service, console and RADIUS server) runs as a virtual appliance on your own VMware ESXi or vSphere. NADs send RADIUS and TACACS+ to the appliance’s address on your network. The appliance can join Active Directory itself to check PEAP-MSCHAPv2 passwords. See Deploy and operate.

A site connector sits on the site network, next to the switches and APs. It:

  • receives UDP RADIUS (1812/1813) from local NADs and forwards it to Airgate over RadSec, or through an HTTPS tunnel when RadSec is not available;
  • delivers CoA and Disconnect messages from Airgate to NADs behind NAT;
  • relays TACACS+ (TCP 49) to Airgate;
  • receives DHCP from an IP helper (UDP 67) to profile devices, without answering DHCP;
  • can be joined to Active Directory to check PEAP-MSCHAPv2 passwords on site;
  • keeps a cache of MAC-authentication answers and uses it while the site cannot reach Airgate.

Connectors only open outbound connections (HTTPS 443 and RadSec 2083). See Sites and site connectors.

© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security