PCAP Triage with tshark
This skill shows a fast workflow to inspect PCAPs with tshark and extract protocol-level details.
See also: suricata-offline-evejson for testing IDS rules against the same PCAPs.
Quick filters
List HTTP traffic:
tshark -r file.pcap -Y http
Filter by method or host:
tshark -r file.pcap -Y 'http.request.method == "POST"'
tshark -r file.pcap -Y 'http.host == "example.com"'
tshark -r file.pcap -Y 'http.host contains "example"'
Inspect requests
Print useful HTTP fields:
tshark -r file.pcap -Y http.request \
-T fields -e frame.time -e ip.src -e tcp.srcport -e http.request.method -e http.request.uri
Follow a TCP stream
To view a request/response conversation:
tshark -q -r file.pcap -z follow,tcp,ascii,0
Change the stream index (0) if there are multiple streams.
Export payload bytes
If you need to examine raw bytes for tricky parsing, use -x:
tshark -r file.pcap -Y http -x
Practical tips
- Start broad (
-Y http), then narrow to one flow/stream. - Confirm where strings live (headers vs body vs URL query).
- Keep notes about invariant parts vs variable parts.
Helper script
For a quick summary across a PCAP (first 50 requests: time, source, method, URI), and optionally a count of requests carrying a given header line, use:
bash scripts/summarize_http_requests.sh <file.pcap> ['X-Header: value']