Packet Analysis & Protocol Inspection
Network telemetry and packet-level inspection provide ground truth regarding host communication, application layer payloads, protocol anomalies, and unauthorized lateral movement.
TCP Handshake & Connection Lifecycles
Section titled “TCP Handshake & Connection Lifecycles”Understanding the flags within the TCP header is required for diagnosing connection issues and interpreting packet captures:
sequenceDiagram autonumber actor Client actor Server Note over Client,Server: 3-Way Handshake (Connection Establishment) Client->>Server: SYN (seq=x) Server->>Client: SYN-ACK (seq=y, ack=x+1) Client->>Server: ACK (seq=x+1, ack=y+1) Note over Client,Server: Data Exchange Client->>Server: PSH-ACK (Data Payload) Server->>Client: ACK Note over Client,Server: Graceful Teardown Client->>Server: FIN (seq=x+n) Server->>Client: ACK (seq=y+m, ack=x+n+1) Server->>Client: FIN (seq=y+m) Client->>Server: ACK (ack=y+m+1)- SYN (Synchronize): Initiates a connection request.
- ACK (Acknowledge): Confirms receipt of previously transmitted packets.
- PSH (Push): Directs the receiving buffer to immediately forward data to the application layer.
- RST (Reset): Abruptly aborts a connection due to an unhandled state, closed port, or firewall drop.
- FIN (Finish): Gracefully informs the remote host that sender has finished transmitting data.
Packet Capture with tcpdump
Section titled “Packet Capture with tcpdump”tcpdump operates in user space utilizing libpcap to capture packets directly from Linux kernel network interfaces.
Common CLI Options
Section titled “Common CLI Options”| Flag | Description |
|---|---|
-i <interface> |
Network interface (eth0, any, tun0). |
-n |
Do not resolve hostnames (prevents reverse DNS queries during capture). |
-nn |
Do not resolve hostnames or port names (displays numeric ports). |
-v, -vv, -vvv |
Increases verbosity (displays TTL, IP IDs, protocol options). |
-X / -XX |
Dumps packet headers and payloads in both Hex and ASCII format. |
-w <file.pcap> |
Writes raw packets to disk in libpcap format without parsing to screen. |
-r <file.pcap> |
Reads and parses an existing PCAP file from disk. |
-c <count> |
Stops capturing after receiving <count> packets. |
Practical BPF Capture Examples
Section titled “Practical BPF Capture Examples”# 1. Capture HTTP traffic on eth0 without DNS lookupsudo tcpdump -i eth0 -nn -c 50 port 80
# 2. Capture all traffic to or from a specific hostsudo tcpdump -i any -nn host 192.168.1.10
# 3. Capture SYN packets only (detect incoming connection attempts / syn sweeps)sudo tcpdump -i eth0 "tcp[tcpflags] & (tcp-syn) != 0 and tcp[tcpflags] & (tcp-ack) == 0"
# 4. Stream capture to PCAP file with 10,000 packet limitsudo tcpdump -i any -nn -w lab_incident_capture.pcap -c 10000Wireshark Display Filters
Section titled “Wireshark Display Filters”While BPF capture filters decide what is written to disk, Wireshark display filters evaluate loaded packets in memory.
High-Value Display Filter Expressions
Section titled “High-Value Display Filter Expressions”| Investigation Goal | Wireshark Display Filter |
|---|---|
| Specific IP Conversation | ip.addr == 192.168.1.10 && ip.addr == 192.168.1.25 |
| All TCP SYN Packets (Probes) | tcp.flags.syn == 1 && tcp.flags.ack == 0 |
| RST Flagged Packets (Resets) | tcp.flags.reset == 1 |
| HTTP POST Data Submissions | http.request.method == "POST" |
| HTTP Error Responses | http.response.code >= 400 |
| DNS Lookups and Queries | dns.flags.response == 0 |
| DNS Server Error Responses | dns.flags.rcode != 0 |
| SMB File Operations | smb2.cmd == 5 (Create/Open) |
Reconstructing Data Streams
Section titled “Reconstructing Data Streams”- Right-click any TCP packet in the Wireshark GUI list.
- Select Follow → TCP Stream (or HTTP Stream).
- Wireshark reassembles fragmented packets in chronological order, displaying client requests in red and server responses in blue.
- Export raw stream binaries for malware or file exfiltration analysis via File → Export Objects → HTTP.