Logs and debugging
When someone does not get on the network, or gets the wrong access, Airgate gives you four levels of detail. Work from the top down: each step shows more than the one before. The Sign-in log and Logs need the monitor:read permission (for example Help Desk); packet capture needs admin:read to view and admin:write to start captures (for example Tenant Administrator).
| Step | Where | Shows |
|---|---|---|
| 1 | Monitor › Sign-in log | Every request: result, diagnosis, the rule that matched, the full policy trace, the attributes sent back |
| 2 | Access › Test access | What a user or device would get now, without a real sign-in |
| 3 | Monitor › Logs with debug logging | What Airgate is doing: directory lookups, integrations, errors, and with debug on one detailed line per sign-in |
| 4 | Monitor › Packet capture | The packets themselves, for Wireshark |
Step 1: The Sign-in log and its trace
Section titled “Step 1: The Sign-in log and its trace”Monitor › Sign-in log lists every RADIUS, TACACS+ and portal sign-in. For a refused sign-in, the list shows a one-line diagnosis, such as Wrong password or Denied: managed by Intune check failed.
Open a record to see:
| Tab | Shows |
|---|---|
| Summary | Result, user, device MAC address, network device, access policy, matched rule, and for a refusal the diagnosis with How to fix |
| Input | The request attributes as the network device sent them |
| Output | The reply attributes Airgate sent back (VLAN, role, ACL and so on) |
| Computed attributes | What Airgate knew when it decided: connection, certificate, device, directory groups, Intune, CrowdStrike or SentinelOne data |
| Trace | Every step of the decision: which policy was selected, which directory was asked, each rule and condition evaluated, and the result |
| Accounting | Accounting records of the session |
The diagnosis titles and their fixes are listed in Troubleshooting.
Step 2: Test access
Section titled “Step 2: Test access”Access › Test access runs a synthetic request through the policy: choose the user or MAC address, the network device and the connection type, and see the policy, rule, role and attributes Airgate would return now, with the same trace. Use it after you change a rule, before you ask the user to reconnect.
Step 3: Logs and debug logging
Section titled “Step 3: Logs and debug logging”Monitor › Logs shows Airgate’s latest log records for your tenant, live.
- Filter by Level (All, Debug, Info, Warning, Error), by Module, or by text: a user name, MAC address, network device address or message.
- Live follows new records as they arrive.
- Select a record to see all its fields.
- Download saves the current view as a text file, for example for a support case.
Normal logging shows warnings, errors and major events. To see each sign-in in detail:
- Next to Debug logging is off, choose 15 min, 30 min or 60 min.
- Reproduce the problem: reconnect the device.
- Set Level to Debug and search for the user or MAC address. Each sign-in has a
RADIUS acceptorRADIUS rejectrecord with the user, MAC address, network device, matched rule, the full policy trace and the reply attributes.
Debug logging turns itself off at the time shown, or select Turn off. It affects only your tenant. Turning it on or off needs admin:write and is recorded in the audit log.
Platform administrators can choose Whole platform to see every tenant’s records and turn on debug logging for every module.
Logs on the appliance
Section titled “Logs on the appliance”On the appliance, the services’ own output is also available over SSH:
sudo airgate-compose logs -f nacd # the Airgate servicesudo airgate-compose logs -f freeradius # RADIUSsudo airgate-compose ps # service statusOn an Airgate Edge connector: sudo journalctl -u nac-edge -f.
Step 4: Packet capture
Section titled “Step 4: Packet capture”Use a capture when the Sign-in log has no record at all (the request never arrived, or the reply never reached the switch), for EAP problems between the client and Airgate, or when a vendor asks for a pcap file.
-
Go to Monitor › Packet capture and fill in New capture.
-
Where:
- Cloud NAC: the traffic between your network devices and Airgate’s RADIUS service. A tenant’s cloud capture includes only the addresses of its own network devices that connect directly (not through a site connector).
- Edge connector: the traffic on a site connector’s host: RADIUS from local switches, DHCP, CoA, TACACS+. Choose the connector.
-
Traffic:
Option Captures RADIUS UDP 1812, 1813, 1645, 1646, 3799 RADIUS + RadSec The above and TCP 2083 TACACS+ TCP 49 CoA / Disconnect UDP 3799, 1700 DHCP UDP 67, 68 LDAP / AD TCP 389, 636, 3268, 3269 Kerberos UDP and TCP 88 Syslog UDP 514, TCP 514, 6514 Custom ports The UDP ports and TCP ports you list -
Duration: 30 seconds to 10 minutes.
-
Optional: Only these hosts (a switch address or subnet, comma-separated) to keep the capture small, and a Name to find it later.
-
Select Start capture and reproduce the problem while it runs. A capture stops after the duration, 10,000 packets or 20 MB. Stop ends it early and keeps what was captured.
-
Download the
.pcapfile and open it in Wireshark.
Captures are deleted after 24 hours. Starting, downloading and deleting a capture needs admin:write and is recorded in the audit log.
Reading RADIUS in Wireshark
Section titled “Reading RADIUS in Wireshark”- To decode passwords and keys, set the network device’s shared secret in Edit › Preferences › Protocols › RADIUS › Shared Secret.
- Useful filters:
radius,radius.code == 3(Access-Reject),radius.User_Name == "alice@contoso.com",eap,eap.code == 4(EAP failure). - RadSec and the inner part of EAP-TLS and PEAP are encrypted; the capture shows only the outer exchange. Use the Sign-in log for what happened inside.
Capturing on a site connector
Section titled “Capturing on a site connector”The connector must be up to date and allowed to capture packets. The nac-edge.service systemd unit grants the packet-capture capability; after installing a new unit file run systemctl daemon-reload && systemctl restart nac-edge. In a container, run the connector with host networking (Docker grants the packet-capture capability by default unless all capabilities are dropped). An older connector leaves a capture running until it times out, then marks it failed.
Misconfigured network devices
Section titled “Misconfigured network devices”Airgate reports network devices that send with the wrong shared secret or from an unknown address under Monitor › Alerts and events (category Network device) and raises the Misconfigured Network Devices alert:
| Problem | Detected by |
|---|---|
| RADIUS with the wrong shared secret | The RADIUS service (requests with a Message-Authenticator, which includes all 802.1X / EAP, and all accounting) and site connectors |
| TACACS+ with the wrong shared secret | The TACACS+ service |
| RADIUS or TACACS+ from an address that is not a known network device | Airgate and site connectors |
| A known device that may not send it: disabled, assigned to a site connector but sending directly, or no secret set for that protocol | Airgate |
Each device is reported at most once every 10 minutes while it keeps sending, and the alert resolves 30 minutes after the last report. A wrong secret on a PAP request without Message-Authenticator cannot be told apart from a wrong password; it shows as a reject in the Sign-in log.