Skip to content

Ports and firewall rules

This page lists the network ports Airgate uses, in both directions, so you can write firewall rules. It covers the Airgate service (appliance or cloud), site connectors and the connections Airgate makes to your network devices and to other services.

Port Protocol From Purpose
1812 UDP Network devices RADIUS authentication (802.1X, MAC authentication, PAP/CHAP/MS-CHAP)
1813 UDP Network devices RADIUS accounting
2083 TCP Network devices with RadSec, site connectors RadSec (RADIUS over TLS, RFC 6614), mutual TLS
49 TCP Network devices TACACS+ (administrator logins on switches, routers, firewalls)
443 TCP Administrators, guests, BYOD users, MDMs, site connectors, API clients HTTPS: console and API (/api/v1/…), guest portals (/portal/…), BYOD portals (/byod/…), SCEP (/scep/…), OCSP (/ocsp/…) and CRLs (/crl/…), site connector API (/edge/…)
80 TCP Devices checking certificates, browsers HTTP: the same routes without TLS, used for OCSP and CRL downloads
67 UDP DHCP relays (IP helper) DHCP fingerprint listener for profiling. Off unless the operator configures its address. It never answers DHCP.
22 TCP Administrators SSH to the Airgate appliance (user airgate). Appliance only, optional.

The appliance also uses internal ports between its own containers (the Airgate service’s internal RADIUS API on 8091, the packet capture agent on 8092, PostgreSQL on 5432). They are not published and need no firewall rule.

Port Protocol To Purpose
3799 (default) UDP Network devices RADIUS CoA and Disconnect-Request (RFC 5176). The port is set per device (CoA port); Cisco IOS defaults to 1700. For devices assigned to a site connector, the connector sends it on the site network instead.
161 (default) UDP Network devices with SNMP turned on SNMP polling for device profiling (LLDP, CDP, ARP). The port is set per device on the SNMP tab.

Outbound from Airgate to directories and services

Section titled “Outbound from Airgate to directories and services”

Only the connections for features you use are needed.

Destination Port Used by
Active Directory and LDAP servers TCP 389 (LDAP, StartTLS) or 636 (LDAPS) Active Directory and Generic LDAP directories
Domain controllers TCP 88 (Kerberos), 389 (LDAP), 445 (SMB), and DNS PEAP-MSCHAPv2 with Active Directory when the appliance itself is domain-joined
ldap.google.com TCP 636 Google Workspace directory (Secure LDAP)
login.microsoftonline.com, graph.microsoft.com TCP 443 Microsoft Entra ID directory, Microsoft Intune device sync, Intune SCEP validation, BYOD Microsoft sign-in
api.manage.microsoft.com and the Intune service addresses Microsoft returns TCP 443 Intune SCEP validation
Your Okta organisation URL TCP 443 Okta directory
Your SQL server TCP 5432 (PostgreSQL), 3306 (MySQL, MariaDB), 1433 (SQL Server) or the configured port Generic SQL DB directory
Your REST API TCP 443 or the configured port HTTP (REST) directory, HTTP enforcement actions, webhooks
External RADIUS or token servers UDP 1812 or the configured port RADIUS server and Token server (RADIUS) directories
CrowdStrike API (api.crowdstrike.com, api.us-2.crowdstrike.com, api.eu-1.crowdstrike.com or api.laggar.gcw.crowdstrike.com) TCP 443 CrowdStrike Falcon device sync
Your SentinelOne management console URL TCP 443 SentinelOne device sync
Your Jamf Pro URL TCP 443 Jamf Pro device sync
standards-oui.ieee.org TCP 443 MAC vendor (OUI) registry downloads for profiling
Your syslog or SIEM collector UDP or TCP 514, TLS 6514, or the configured port Log export (syslog)
Your Splunk HTTP Event Collector TCP 443 or the configured port Log export (Splunk HEC)
Your Power Automate workflow URL TCP 443 Guest sponsor messages in Microsoft Teams
Your SMTP relay TCP 587 or the configured port Guest e-mail receipts and notifications
Your SMS gateway (for example api.twilio.com) TCP 443 Guest SMS
Your SFTP backup server TCP 22 or the configured port Appliance backup copies
Port Protocol From Purpose
1812 UDP Site network devices RADIUS authentication
1813 UDP Site network devices RADIUS accounting
49 TCP Site network devices TACACS+ (when TACACS+ tunnel is on)
67 UDP DHCP relays (IP helper) DHCP fingerprints (when DHCP fingerprinting is on); never answers DHCP
22 TCP Administrators SSH to the Airgate Edge appliance (optional)
Destination Port Purpose
Airgate console address TCP 443 Enrolment, configuration, heartbeat, CoA jobs, TACACS+ tunnel, DHCP observations, HTTPS tunnel for RADIUS
Airgate RadSec address TCP 2083 RadSec for RADIUS. Without it, RADIUS goes through the HTTPS tunnel.
Site network devices UDP 3799 or the device’s CoA port CoA and Disconnect delivery
Domain controllers TCP 88, 389, 445, and DNS PEAP-MSCHAPv2 checks when the connector is domain-joined

A site connector needs no inbound rule from the internet.

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