10 Wireshark Display Filters You'll Use Every Week
Display filters turn a million-packet capture into an answer. Ten patterns that cover 90% of real troubleshooting, plus the two mistakes everyone makes.
The security-footage analogy
Imagine a convenience store with 20 cameras recording around the clock. When something goes wrong, nobody watches all 20 feeds end to end — you search: "show me camera 4 between 2 and 3 a.m." Wireshark's display filter is that search box. The full recording (the capture file) stays intact; the filter just decides which moments appear on screen. A capture filter, by contrast, is deciding before the incident which cameras even record — great for saving disk, terrible if you guessed wrong and the crucial camera was off.
The one distinction that matters
Wireshark speaks two filter languages. Capture filters (BPF, Berkeley Packet Filter — the kernel-level syntax used when capturing) decide what gets recorded — syntax like host 192.168.1.10 and tcp port 443. Display filters hide what you don't want to see after the fact — syntax like ip.addr == 192.168.1.10 && tcp.port == 443. Capture filters save disk; display filters save sanity. Watch the difference:
Watch: a display filter at work
Six packets stream past. The filter tcp.port == 443 keeps the HTTPS traffic bright and dims the rest:
The ten
Each of these is a display filter (Wireshark syntax). The Wireshark display filter builder tool on this site constructs them for you — but knowing what they mean is what makes you fast in an incident:
- ip.addr == 192.168.1.10 — everything to or from a host. Use ip.src/ip.dst when direction matters.
- tcp.port == 443 — a service across all hosts. Combine: tcp.port == 443 && ip.addr == 192.168.1.10.
- dns — all DNS. Pairs with dns.qry.name contains "example.com".
- icmp — ping and traceroute. Split with icmp.type == 8 / == 0.
- arp — who-has traffic. Flooding ARP is a classic misconfig signature.
- tcp.flags.syn == 1 && tcp.flags.ack == 0 — new connection attempts. SYNs with no SYN-ACK = down or filtered.
- tcp.analysis.retransmission — the start of every "it's slow" case.
- http.response.code >= 400 — failing HTTP.
- frame.len > 1400 — jumbo or fragmented traffic patterns.
- tcp.stream eq 7 — one TCP conversation; right-click any packet → Follow → TCP Stream does this for you.
Try it: click a filter, see the bytes it matches
Below is one real frame — Ethernet + IPv4 + TCP, 54 bytes — as Wireshark would dissect it. Click any filter chip to light up the exact bytes that filter looks at:
Click a filter above — matching bytes highlight in amber.
offset 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 0000 00 1b 2c 3d 4e 5f 00 1a 2b 3c 4d 5e 08 00 45 00 0010 00 36 1c 46 40 00 40 06 6b 2c c0 a8 01 0a 5d b8 0020 d8 22 cc 75 01 bb 8f 2c 41 d0 5e 11 22 33 50 18 0030 fa f0 9a bc 00 00