Skip to content

Identify device types with the profiler

The profiler classifies every device Airgate sees into a category (Printer, VoIP Phone, Computer…), a family (Windows, Apple iOS, HP…) and a device name, with a confidence. Access policies can then match the type: “IP cameras get the camera VLAN”. This guide connects the evidence sources and shows how to read and tune the result.

The profiler collects evidence about each MAC address and runs fingerprint rules over it:

Evidence Where it comes from
DHCP fingerprint: option 55 (parameter request list, in wire order), option 60 (vendor class), option 12 (host name), option order DHCP packets relayed to a site connector or to Airgate’s DHCP listener, or RADIUS accounting with Cisco device-sensor or Aruba AOS-CX data
HTTP User-Agent and client hints Guest and BYOD portal visits
MAC vendor (IEEE OUI registry) The MAC address itself. Ignored for random (private) MACs.
Network-device attributes RADIUS data such as Aruba-Device-Type, CDP and LLDP TLVs from device-sensor
LLDP and CDP neighbours SNMP polling of your switches

Each rule that matches gives evidence with a priority and a confidence. Higher priority wins (self-identifying strings, CDP, LLDP and SNMP 80, device User-Agents 75, the built-in User-Agent parser 70, DHCP fingerprints 50 to 60, host names 20, OUI 10; your own rules default to 100). A device counts as profiled when it has a category and a confidence of at least 50; the device name is published from 60.

The profiler is careful about changing an existing profile: a different verdict must be at least 10 points more confident than the current one. When a headless device (printer, phone, camera, access point…) suddenly looks like a computer or smartphone with confidence 70 or more, the profile is kept and the device gets the attributes Conflict = true, Other Category, Other OS Family and Other Device Name: a likely MAC spoofer.

Profiles set by an administrator (Lock profile (manual)) are never changed by the profiler.

  • Switches and access points under Network › Switches and APs.
  • To collect DHCP from a site: a site connector under Network › Sites on a server that the site’s routers can reach on UDP 67. A site connector only listens: it never answers DHCP.
  • An administrator role with identity:read to view, identity:write to reprofile, and policy:write for fingerprint rules and SNMP settings.

DHCP fingerprints are the most useful evidence for headless devices. Use one or more of these sources.

On the router or layer-3 switch of each client VLAN, add an extra ip helper-address pointing at the site connector, next to your real DHCP server. The DHCP server keeps answering; the connector only reads the copy.

interface Vlan40
ip helper-address 10.0.0.53 ! your DHCP server
ip helper-address 10.0.0.60 ! Airgate site connector (copy only)

Aruba AOS-CX:

interface vlan 40
ip helper-address 10.0.0.53
ip helper-address 10.0.0.60

The site connector pushes the packets to Airgate, which assigns them to your tenant. If your Airgate platform runs its own DHCP listener (the DHCP card on Devices › Device types shows Listening), you can relay to the Airgate address instead. Airgate then accepts a packet only when its source address, or the relay address (giaddr) of a packet from a private address, belongs to one of your network devices.

RADIUS accounting with device-sensor (Cisco)

Section titled “RADIUS accounting with device-sensor (Cisco)”

Cisco switches can add DHCP options, CDP and LLDP data to RADIUS accounting. Airgate decodes the dhcp-option, cdp-tlv, lldp-tlv and http-tlv values:

device-sensor filter-list dhcp list DS-DHCP
option name host-name
option name parameter-request-list
option name class-identifier
device-sensor filter-spec dhcp include list DS-DHCP
device-sensor accounting
device-sensor notify all-changes
radius-server vsa send accounting
aaa accounting dot1x default start-stop group AIRGATE

Aruba AOS-CX switches that send DHCP data in Aruba-AVPair accounting are decoded too.

SNMP polling reads the LLDP and CDP neighbour tables of your switches (IP phones, access points, other switches) and, optionally, the ARP table to learn IP addresses. It only reads; nothing is written to the device.

  1. Open Network › Switches and APs, edit a switch and select the SNMP tab.
  2. Turn on Read this device over SNMP, choose Version (v1, v2c or v3), and enter the Community string or the v3 Username, Auth password and Privacy password.
  3. Save.

Airgate polls such devices about every hour. Only single-address devices that Airgate reaches directly are polled (not subnets, not devices behind a site connector). Devices › Device types › SNMP polling shows the last poll per device.

Open Devices › Device types. The page shows:

  • Endpoints, Profiled, Unprofiled, Randomized MACs, Conflicts and Profiled · 24h tiles;
  • distributions by Device categories, Device families, MAC vendors and Profile sources;
  • Collectors: the DHCP, SNMP, OUI registry and fingerprint-rule status;
  • tabs Recently profiled, Recent changes, Unknown fingerprints (unprofiled devices grouped by DHCP fingerprint), DHCP observations, Profile history and SNMP polling.

On a single device (Devices › Devices › the MAC), the Fingerprints tab shows the evidence and the classification trace.

After you change rules, select Reprofile… to re-run the classification for unprofiled devices or for all devices.

For devices the built-in rules do not know, add a tenant rule. Fingerprint rules are managed through the API (policy:write):

POST /api/v1/t/contoso/fingerprint-rules
Content-Type: application/json
{
"name": "AcmeCam cameras",
"priority": 100,
"confidence": 90,
"category": "Physical Security",
"family": "Acme",
"device_name": "AcmeCam $1",
"match": { "dhcp_vendor": "^AcmeCam (\\S+)", "oui": ["00:aa:bb"] }
}

Match conditions (all non-empty conditions must hold):

Field Syntax
dhcp_fingerprint (option 55), dhcp_options (option order) 1,3,6,15 exact, 1,3,6,* prefix, ~43,150 contains all, a|b alternatives
dhcp_vendor, hostname, user_agent, mac_vendor Go RE2 regular expression; (?i) for case-insensitive; capture groups feed $1 in the verdict
oui MAC prefixes of 6 to 11 hex digits. Never matches random MACs.
attributes up to 16 fact attributes → regex, for example cdp.platform, lldp.sys_desc, aruba.device_type

Test a rule without saving with POST /fingerprint-rules/test. A tenant can have up to 1,000 rules. Then select Reprofile… on Devices › Device types to apply them to existing devices.

Step 5: Use device types in access policies

Section titled “Step 5: Use device types in access policies”

In Access › Access policies, add a condition Device type is with the category, for example Physical Security (cameras) or Printer (matched ignoring case, on Endpoint:Category). See Devices by MAC address.

When a device’s category or family changes, Airgate can re-authorize its session with a CoA so the new rule applies. This is a setting of the RADIUS service (profiler_enabled, profiler_categories, profiler_coa_profile_id), available through the API; at most one CoA per device per minute and three per hour. See Change of Authorization.

  • Devices › Device types › DHCP observations: packets arrive with the source edge (site connector), dhcp (listener) or RADIUS.
  • A test device appears under Recently profiled with the expected category.
  • Access › Test access with the device’s MAC: the rule with Device type is matches.
Symptom Cause Fix
DHCP observations stays empty The extra helper address is missing, UDP 67 to the site connector is blocked, or the relay’s address is not one of your network devices. Check the helper address and firewall; add the relaying router under Switches and APs.
The DHCP collector shows Listener off The platform’s own DHCP listener is not enabled. Relay to a site connector instead.
Many devices under Randomized MACs stay unprofiled Phones and laptops use private MACs; vendor (OUI) rules never match them. Rely on DHCP and User-Agent evidence, or identify them by certificate.
A printer shows Conflict A device with the printer’s MAC now looks like a computer: possible MAC spoofing. Check the switch port; add a rule that denies or quarantines devices with Conflict = true.
Sign-in log: Denied: endpoint:Category check failed The device is not profiled yet, or the rule uses another category name than the profiler (for example IP Camera instead of Physical Security). Check the category on the device; use the exact category name in the rule.
A manual profile never changes Locked profiles are never reprofiled. Release the manual profile on the device.
© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security