Packet captures from zero: capture, filter, read
▶ Start the interactive lesson
A user swears "the internet is broken". Your manager says: "Get a capture." You open Wireshark for the first time and it's a waterfall: thousands of lines a second, colours everywhere, words like SYN, ACK, ARP, DNS. Sam leans over: "Wireshark is just a very honest witness. It shows you exactly…
What a capture is
A packet capture records every packet your network card sees: who sent it, who it was for, which protocol, and what's inside. Saved captures are .pcap or .pcapng files.
Where you capture matters
You only see traffic that passes the point where you capture. Capturing on your own laptop shows your laptop's traffic, not your colleague's.
Two kinds of filter
Capture filters decide what gets recorded at all. They use a simpler syntax, e.g. host 10.1.1.5 and port 443. Use them to keep files small on busy links.
Handy tools inside Wireshark
Follow TCP Stream (right-click a packet): shows one whole conversation on its own.
Key points
- A capture is an honest record of what crossed the wire. Read list → details.
- Where you capture decides what you see. Use SPAN or a TAP, and capture at both ends for path problems.
- Capture filters limit what's recorded; display filters narrow what you look at.
- Use Follow stream, Conversations and Expert info to find the story fast.
Words you'll learn
Packet capture (pcap) · Capture filter (BPF syntax) · Display filter · SPAN / port mirroring · Network TAP · Follow TCP stream · Expert information · tcpdump / tshark