How to capture network traffic

A capture is a recording of the packets your device sends and receives. Start it right before you reproduce the problem, stop it right after, and upload the file.

Only capture traffic you're allowed to.

Capture your own device or a network you manage. Captures can include addresses, names, and anything sent without encryption, so treat the file like a private document.

Any computer: Wireshark

Wireshark is free and works on Windows, macOS, and Linux. It's the easiest option if you can install software.

  1. Install Wireshark from its official website and open it.
  2. Pick the interface your traffic uses: usually Wi-Fi or Ethernet. The one with a moving activity line is the busy one.
  3. Click the blue fin icon to start capturing, reproduce the problem, then click the red square to stop.
  4. Choose File → Save As and save as .pcapng.

Windows, without installing anything

Windows 10 (version 2004 and later) and Windows 11 include pktmon. Open Terminal (Admin) or Command Prompt as administrator, then:

pktmon start --capture --comp nics
rem ...reproduce the problem...
pktmon stop
pktmon etl2pcap PktMon.etl --out capture.pcapng

--comp nics records only at the network adapters, so each packet appears once. Upload capture.pcapng.

macOS: tcpdump

macOS includes tcpdump. Find your interface name (Wi-Fi is usually en0):

networksetup -listallhardwareports

Then capture, and press Ctrl+C to stop:

sudo tcpdump -i en0 -w capture.pcap

Linux: tcpdump

Install tcpdump from your distribution's packages if it's missing. To record every interface:

sudo tcpdump -i any -w capture.pcap

Or list interfaces with ip link and capture one, for example -i eth0. Press Ctrl+C to stop.

Getting a useful capture

  • Keep it short. Start right before the problem and stop right after. Short captures are easier to read and stay under the 100 MB limit.
  • Capture on the device with the problem, so both directions of its traffic are recorded.
  • Narrow it down if it's busy. A capture filter records only what matters, for example tcpdump -i en0 -w capture.pcap host 203.0.113.10 or port 443.
  • Remember encryption. HTTPS contents stay encrypted in the capture. Addresses, names, and timing are still visible, which is usually enough to find connection problems.

Not ready to capture? Practice with a sample capture first.