Sites and site connectors
A site connector (in the API: edge connector) is a small Airgate program that runs at a customer site, next to the switches and access points. It carries local traffic to Airgate over outbound connections, so the site needs no inbound firewall rules and network devices behind NAT still work. This page explains what a connector does and how it behaves. Connectors are managed on Network › Sites.
Why use a site connector
Section titled “Why use a site connector”Sending plain UDP RADIUS from every switch straight to the cloud has drawbacks: RADIUS over UDP is only protected by the shared secret, CoA cannot reach network devices behind NAT, and the cloud cannot reach an on-premises Active Directory. A connector solves all three.
Use a connector when:
- network devices speak only UDP RADIUS and are behind NAT, or share an address with other devices;
- you need CoA (guest portals, revocations, operator actions) to reach those devices;
- you use PEAP-MSCHAPv2 with an on-premises Active Directory and Airgate runs in the cloud;
- you want DHCP-based device profiling at the site;
- MAC-authenticated devices (cameras, printers) must stay on their VLAN through a WAN outage.
Network devices that support RadSec can connect to Airgate directly instead.
What a connector relays
Section titled “What a connector relays” Site network Airgate ┌─────────────────────────────────────────┐ │ switches / APs ──UDP 1812/1813──▶ ┐ │ RadSec (TCP 2083, mutual TLS) │ │ │ ─────────────────────────────▶ RADIUS server │ switches ──TCP 49 (TACACS+)──▶ site │ or HTTPS tunnel (TCP 443) │ DHCP helper ──UDP 67────────▶ connector │ │ │ │ HTTPS (TCP 443): enrolment, config, │ switches / APs ◀──UDP 3799 (CoA)── ┘ │ heartbeat, CoA jobs, TACACS+ tunnel, │ domain controllers ◀── ntlm_auth (opt.) │ DHCP observations, AD checks └─────────────────────────────────────────┘| Function | Detail |
|---|---|
| RADIUS | Receives UDP RADIUS (1812 authentication, 1813 accounting) from the network devices assigned to it, and forwards each request to Airgate tagged with the original device address. Airgate identifies the network device by that address within the connector’s tenant, so private addresses that overlap with other customers are not a problem. |
| CoA and Disconnect | Airgate sends CoA jobs down the HTTPS channel; the connector delivers them to the network device on the site network and reports the answer. |
| TACACS+ | Tunnels TACACS+ sessions (TCP 49) from site devices to Airgate’s TACACS+ server. Turn it on with TACACS+ tunnel. |
| DHCP fingerprints | Listens on UDP 67 as an extra ip helper-address target, never answers DHCP, and pushes the fingerprints to the profiler. Turn it on with DHCP fingerprinting. |
| Active Directory checks | A connector host joined to the domain runs Samba ntlm_auth for PEAP-MSCHAPv2 and MS-CHAP users of the site’s Active Directory. Airgate asks an online, domain-joined connector first. |
| Packet capture | Captures packets on the connector host for Monitor › Packet capture. |
RADIUS transport
Section titled “RADIUS transport”The connector forwards RADIUS in one of two ways. Choose it under RADIUS transport to the cloud:
| Option | Behaviour |
|---|---|
| Auto (recommended) | RadSec (TLS, TCP 2083) when the connector holds a certificate, otherwise the HTTPS tunnel. |
| RadSec | Same as Auto, but the connector logs a warning while it has no RadSec certificate. |
| HTTPS tunnel | Always relay RADIUS over HTTPS. For sites that cannot reach TCP 2083. |
The RadSec certificate comes from the tenant’s NAD CA when the connector enrols, and is renewed automatically.
Enrolment
Section titled “Enrolment”- On Network › Sites, select Add site, name it and choose the services.
- Issue a one-time enrollment token (it starts with
et_). It is shown once and is valid for the time you choose. - Install the connector at the site: the Airgate Edge appliance (
airgate-edge-<version>.ova, 2 vCPU, 2 GB RAM, 16 GB disk) or the container image. Give it the console address and the token. - The connector enrols, receives its certificate and configuration, and shows as online within a minute.
- Assign network devices to it: on Network › Switches and APs, set Site connector on each device, or use the bulk action Assign selected devices to a site connector. A connector serves exactly the enabled devices assigned to it.
- Point those devices’ RADIUS (UDP 1812/1813), TACACS+ (TCP 49) and DHCP helper (UDP 67) at the connector’s site address.
The connector checks the console’s certificate, so the console’s name must resolve at the site. Turning a site off (Enabled) refuses every API call, RadSec connection, relayed request, CoA relay and TACACS+ tunnel of that connector.
WAN outage
Section titled “WAN outage”If the site loses its link to Airgate:
| Traffic | Behaviour |
|---|---|
| MAC authentication of devices Airgate accepted before | The connector answers from its offline cache: the last answer Airgate gave for the same network device, MAC address and SSID, with a session timeout of 30 minutes so the device re-checks soon after the link returns. Entries are kept for 24 hours by default. A reject from Airgate removes the device from the cache. |
| 802.1X sign-ins | Not answered. EAP needs Airgate. Sessions that are already connected stay connected until the network device re-authenticates them. |
| Unknown devices | Not answered. |
While the link is down, every request still tries Airgate first (that is how the connector notices the link is back), for at most 2 seconds before the cache answers.
Monitoring a connector
Section titled “Monitoring a connector”Network › Sites shows each connector’s status, version, transport, the devices it serves, its counters (RADIUS requests and replies, CoA jobs, DHCP packets, TACACS+ sessions) and anything that needs attention. Wrong shared secrets and unknown devices seen by a connector appear under Monitor › Alerts and events.