Devices and profiling
Airgate keeps a record (an endpoint) for every device it sees, keyed by MAC address. Policies use these records to decide on MAC authentication, to tell device types apart and to check compliance. This page explains the records, their statuses, private Wi-Fi addresses, MAC lists and automatic device types (profiling).
Endpoint records
Section titled “Endpoint records”An endpoint is created or updated when Airgate learns about a MAC address:
- an accepted sign-in (802.1X, MAC authentication, web login): Airgate records the last switch or AP, SSID, sign-in time, tags and, for user sign-ins, the owner;
- RADIUS accounting from a NAD: IP address and last-seen time;
- profiling evidence (DHCP, HTTP User-Agent, SNMP);
- the device syncs from Intune, Jamf Pro, CrowdStrike and SentinelOne;
- a BYOD onboarding, a guest portal login or a Wi-Fi pass;
- an administrator: Devices › Devices (add, edit, import from CSV, bulk changes).
The record holds the MAC address, status, description, owner, device type (category, OS family, device name and confidence), MAC vendor, hostname, IP address, first and last seen, the last sign-in, MAC caching state and custom attributes. Integrations add their facts as attributes, for example Intune Compliance State or SentinelOne Infected. Rules read all of it in the Endpoint namespace. See the policy attributes reference.
Device status
Section titled “Device status”| Status | Meaning | Effect |
|---|---|---|
| Unknown | Airgate has seen the device, but nobody has approved it. New devices start here. | Known devices only MAC policies treat it as not found. Rules can test Device is Not known yet, for example to send it to a registration VLAN. |
| Known | An administrator, an import, a guest portal login or a post-authentication profile marked it as known. | Rules can test Device is Known (added to Devices). |
| Disabled | Blocked. | MAC authentication against Devices is rejected with User account disabled (code 202). Disabled endpoints are never purged automatically. |
Post-authentication enforcement profiles can change a status as part of a decision: [Update Endpoint Known], [Update Endpoint Unknown] and [Update Endpoint Disabled].
Cleanup
Section titled “Cleanup”Settings › General › Data retention & cleanup can delete endpoints that have not been seen for a number of days: Purge Unknown endpoints after, Purge Known endpoints after and Purge randomized-MAC endpoints after. Each is off when set to 0. Disabled endpoints and unexpired MAC-authenticated guests are never purged.
Private Wi-Fi addresses (MAC randomisation)
Section titled “Private Wi-Fi addresses (MAC randomisation)”Phones, tablets and laptops join Wi-Fi with a private, randomised MAC address by default (Apple Private Wi-Fi Address, Android Randomized MAC, Windows Random hardware addresses). A randomised address is a locally administered address: the second-lowest bit of its first byte is set (the second hex digit is 2, 6, A or E).
Airgate detects these addresses:
Connection:Client-Mac-Randomizedistruefor a request from a randomised address;Endpoint:Randomized-MACistrueon the device record, and Devices marks the device with R (MAC type: Randomized);- the profiler ignores the MAC vendor (OUI) of a randomised address, because it does not identify the manufacturer.
A randomised address does not match the hardware MAC address that Intune, Jamf, CrowdStrike or SentinelOne report. For managed devices with Intune certificates, Airgate can match the device by its Intune device ID instead. See Device compliance.
MAC lists
Section titled “MAC lists”Devices › MAC lists holds named lists of MAC addresses or IP addresses (engine name: static host lists), for example Printers or Cameras. A list’s Host type is MAC address or IP address, and its Host format is one of:
| Host format | Entries |
|---|---|
| List | Exact addresses. Partial MAC addresses match as prefixes. |
| Subnet / prefix | For IP addresses, CIDRs (10.0.0.0/8) and ranges (10.0.0.1-50). For MAC addresses, prefixes or OUIs (aa:bb:cc or aa:bb:cc:00:00:00/24). |
| Regular expression | RE2 regular expressions, not anchored. |
A list holds up to 10,000 entries. Lists are used:
- in rule conditions: Device is in MAC list (
Connection:Client-Mac-Address BELONGS_TO_GROUP <list>); - as a Static Host List directory for MAC authentication.
Device types (profiling)
Section titled “Device types (profiling)”The profiler classifies each device into a category (for example Computer, SmartDevice, Printer or VoIP Phone), an OS family (for example Windows, macOS, Apple iOS, Android or Linux) and a device name, with a confidence score. Devices › Device types shows the results and the rules.
Evidence
Section titled “Evidence”| Source | How it reaches Airgate |
|---|---|
| DHCP fingerprint (option list, vendor class, hostname) | DHCP sent to a site connector as an extra ip helper-address target (UDP 67; the connector never answers DHCP). The Airgate service also has its own DHCP listener, which is off unless the operator configures its address. RADIUS accounting and Cisco device-sensor attributes carry DHCP data too. |
| HTTP User-Agent | The guest and BYOD portals record the browser’s User-Agent. |
| MAC vendor (OUI) | The IEEE registry, downloaded and refreshed by Airgate. Ignored for randomised addresses. |
| RADIUS attributes | Accounting and device-sensor data from the NAD. |
| SNMP | Airgate can read network devices over SNMP (LLDP and CDP neighbours, ARP tables). Turn it on per device on the SNMP tab of Network › Switches and APs. |
Each piece of evidence that matches a fingerprint rule (built-in system rules plus your own) proposes a classification. Higher-priority sources win; later evidence must agree or is recorded as a conflict. A device counts as profiled from a confidence of 50, and its device name is published from 60. A profile you set by hand has confidence 100 and is never overwritten by the profiler.
Conflicts
Section titled “Conflicts”A device in a category that never runs a user operating system (printer, VoIP phone, camera, switch and similar) that suddenly looks like a computer or phone raises a profile conflict. It often means someone copied the device’s MAC address. Rules can test it, and Airgate can re-authenticate the session (see below).
Profile changes and CoA
Section titled “Profile changes and CoA”When a device’s category or OS family changes, or a conflict is raised, Airgate can send a CoA to re-authenticate its active sessions, so that the policy decides again with the new type. This happens for sessions whose access policy has profiling enabled (configured through the API), at most once per minute and three times per hour per device.