Admit printers, cameras and IoT devices by MAC address
Printers, IP cameras, door controllers, TVs and other headless devices cannot sign in with 802.1X. With MAC authentication bypass (MAB), the switch or access point sends the device’s MAC address to Airgate as the user name, and Airgate decides by rules: known printers get the printer VLAN, cameras get the camera VLAN and ACL, unknown devices are refused or quarantined.
Before you begin
Section titled “Before you begin”- The switches and access points are added under Network › Switches and APs with a RADIUS shared secret.
- An administrator role with
identity:write(devices, MAC lists) andpolicy:write(access policies). - The VLANs and ACLs you want to assign exist on the switches.
Step 1: Turn on MAC authentication on the network
Section titled “Step 1: Turn on MAC authentication on the network”-
Wired: enable MAB on the access ports, with Airgate as RADIUS server. Ports that also serve PCs can try 802.1X first and fall back to MAB. Cisco IOS-XE example (replace the names):
interface GigabitEthernet1/0/10switchport mode accessauthentication port-control autoauthentication order dot1x mabauthentication priority dot1x mabmabdot1x pae authenticatorAruba AOS-CX example:
interface 1/1/10aaa authentication port-access mac-authenable -
Wi-Fi: on an SSID for devices, enable MAC authentication against RADIUS (often with WPA2-Personal).
Step 2: Tell Airgate about the devices
Section titled “Step 2: Tell Airgate about the devices”Use whichever fits:
| Way | When |
|---|---|
| Devices › Devices › Add device | A few devices. Enter the MAC address, set Status to Known, and optionally Owner, Description, Category (for example Printer). Setting a category, family or device name locks the profile: the profiler will not reclassify it. |
| Devices › Devices › Import | A CSV with a MAC column (mac, MAC Address, Calling-Station-Id…). Choose When the MAC already exists and Status of new endpoints without a status column. Unknown columns become custom attributes. |
| Devices › Devices › Bulk edit | Paste a list of MACs and change their status (for example to Known) in one go. |
| Devices › MAC lists | Group MACs by purpose (Printers, Cameras) and match the list in a rule. See MAC lists. |
| Device type | The profiler types devices automatically (Printer, Physical Security for cameras, VoIP Phone…) from DHCP, MAC vendor and other signals. See device profiling. |
Device status meanings:
| Status | MAC authentication |
|---|---|
| Known | Found in the [Endpoints Repository]. |
| Unknown | Not approved yet. Fails unless the policy allows any device. |
| Disabled | Blocked. MAC authentication is rejected. |
Step 3: Create the access policy
Section titled “Step 3: Create the access policy”-
Open Access › Access policies › Add a policy and choose IoT and printers. It creates a policy with Connection MAC authentication, Which devices Any device, and a rule
Known devices. -
Set Name (for example
IoT) and, for Wi-Fi, Wi-Fi networks (SSID). To limit the policy to some switches, pick a group in Switches and APs. -
Edit the rules (Add a rule, then Add condition):
Order Rule When Then 1 PrintersDevice is in MAC list PrintersAllow, VLAN 402 CamerasDevice type is Physical SecurityAllow, VLAN 50, ACL or firewall policyCAMERAS-ONLY3 Known devicesDevice is Known (added to Devices) Allow, VLAN 60Default Deny -
Select Save changes and order the policy with the arrows: the first policy that matches handles the sign-in.
Which devices choices:
- Any device: every MAC reaches the rules, also devices not known yet. Use it with rules like the table above, or to quarantine unknown devices with a last rule Device is Not known yet → Allow, quarantine VLAN.
- Known devices only: devices that are not Known in Devices are refused before the rules run.
Verify
Section titled “Verify”- Access › Test access, Test A device (MAC address): enter the MAC, optionally the SSID and switch address, and select Run test. The result shows the policy, rule and attributes without touching the network.
- Monitor › Sign-in log: each MAB request with the MAC, the Rule that matched and the VLAN in the record’s Output.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| Sign-in log: No access policy handles this sign-in | No policy matches this switch, SSID or connection type. | Check Connection (MAC authentication), the SSID and the switch group of the policy. |
| Sign-in log: No account named “aa:bb:cc:dd:ee:ff” | Known devices only and the device is not Known. | Add the device and set it to Known, or use Any device with rules. |
| Sign-in log: The account is disabled | The device’s status is Disabled. | Set it to Known if it should get in. |
| Sign-in log: Denied: device status check failed | Any device, but no rule matched (for example the device is Unknown). | Add the device or a rule for it. |
| The device gets in but lands in the wrong VLAN | A rule higher in the list matched first. | Order the rules from most to least specific. |
| No MAB request in the Sign-in log | The port or SSID is not doing MAB, or the switch is not a known device. | Check the switch configuration and Switches and APs. |