Packet capture
Packet capture records packets between your network devices and Airgate for a short time and gives you a .pcap file to open in Wireshark. Use it when the Sign-in log does not explain a problem, for example to check whether a switch sends RADIUS at all or whether its shared secret is right.
What this page shows
Section titled “What this page shows”Monitor › Troubleshooting › Packet capture has two cards:
- New capture: the form to start a capture. Shown only to roles that can start captures.
- Captures: the captures of the tenant, newest first. Captures are kept for 24 hours.
A capture runs in one of two places:
- Cloud NAC: in the Airgate cloud, next to the RADIUS service. A cloud capture only includes traffic from your network devices that send RADIUS straight to the cloud; their addresses are listed under the form. Devices behind an edge connector reach the cloud through the connector, so capture on the connector instead. If none of your devices sends RADIUS straight to the cloud, the page says so and starts on Edge connector.
- Edge connector: on one of your edge connectors. It captures every interface of the connector’s host; the connector needs the
NET_RAWcapability. If the connector is offline, the capture starts when it reconnects.
A capture stops after the chosen duration, 10,000 packets or 20 MB, whichever comes first.
Fields and columns
Section titled “Fields and columns”New capture
Section titled “New capture”| Field | Meaning |
|---|---|
| Where | Cloud NAC or Edge connector. |
| Edge connector | The connector to capture on (shown for Edge connector; offline connectors are marked). |
| Traffic | A preset, or Custom ports (see below). |
| Duration | 30 s, 1 min (default), 2 min, 5 min or 10 min. |
| UDP ports, TCP ports | For Custom ports: comma-separated ports, for example 1812, 1813. At least one port is required. |
| Only these hosts | Optional NAD or client addresses or subnets, comma separated, for example 10.0.0.5, 10.0.0.0/24. For a cloud capture, every address must belong to one of your network devices. |
| Name | Optional, for example the ticket number. |
| Traffic preset | Ports |
|---|---|
| RADIUS | UDP 1812, 1813, 1645, 1646, 3799 |
| RADIUS + RadSec | Adds TCP 2083 (TLS: encrypted in the capture) |
| TACACS+ | TCP 49 |
| CoA / Disconnect | UDP 3799, 1700 |
| DHCP | UDP 67, 68 (device profiling; edge connectors) |
| LDAP / AD | TCP 389, 636, 3268, 3269 |
| Kerberos | UDP/TCP 88 |
| Syslog | UDP 514, TCP 514, 6514 |
Captures
Section titled “Captures”| Column | Meaning |
|---|---|
| Capture | Name (or preset), where it ran (Cloud or Edge: connector), duration and the number of host filters. |
| Status | Queued, Capturing (with the time left), Done, Failed (with the error) or Cancelled. A capture that ended early shows packet limit reached, size limit reached or stopped early. |
| Packets | Number of packets and file size, once done. |
| Started | When the capture was started, and by whom. |
While a capture runs, the list refreshes every 3 seconds.
Actions
Section titled “Actions”| Action | What it does |
|---|---|
| Start capture | Starts the capture. Reproduce the problem while it runs. |
| Stop | Stops a queued or running capture early. |
| .pcap | Downloads the capture file, capture.pcap. |
| Delete | After confirmation, deletes the capture and its file. |
| Refresh | Reloads the list. |
To read RADIUS in Wireshark, open the file, then set Edit › Preferences › Protocols › RADIUS › Shared Secret to see decoded passwords and Message-Authenticator checks. RadSec (TCP 2083) is TLS and stays encrypted.
Platform administrators also see This tenant and Whole platform (cloud, unrestricted); the platform view captures in the cloud without the address restriction.
Permissions
Section titled “Permissions”- View:
admin:read: Tenant Administrator, Network Administrator, Read-only Administrator and Platform Administrator. - Change/act: starting, stopping, downloading and deleting captures need
admin:write: Tenant Administrator and Platform Administrator.