π‘ Wireshark Packet Analyzer
Dive deep into network traffic with an interactive packet analyzer simulator. Inspect real-world protocol interactions, decode packet structures, and master the art of network forensics β all from your browser.
What is Wireshark?
Interactive Packet Analyzer Simulator
| No. | Time | Source | Destination | Protocol | Length | Info |
|---|---|---|---|---|---|---|
| 1 | 0.000000 | 192.168.1.100 | 8.8.8.8 | DNS | 72 | Standard query 0x0123 A example.com |
| 2 | 0.002345 | 8.8.8.8 | 192.168.1.100 | DNS | 82 | Standard response 0x0123 A 93.184.216.34 |
| 3 | 0.003100 | 192.168.1.100 | 93.184.216.34 | TCP | 70 | 49152 β 80 [SYN] Seq=0 Win=64240 |
| 4 | 0.012500 | 93.184.216.34 | 192.168.1.100 | TCP | 70 | 80 β 49152 [SYN, ACK] Seq=0 Ack=1 Win=64240 |
| 5 | 0.012600 | 192.168.1.100 | 93.184.216.34 | TCP | 54 | 49152 β 80 [ACK] Seq=1 Ack=1 Win=64240 |
| 6 | 0.013000 | 192.168.1.100 | 93.184.216.34 | HTTP | 148 | GET /index.html HTTP/1.1 |
| 7 | 0.045200 | 93.184.216.34 | 192.168.1.100 | HTTP | 520 | HTTP/1.1 200 OK (text/html) |
| 8 | 0.045300 | 192.168.1.100 | 93.184.216.34 | TCP | 54 | 49152 β 80 [ACK] Seq=95 Ack=467 Win=63720 |
| 9 | 0.045800 | 192.168.1.100 | 93.184.216.34 | HTTP | 152 | GET /logo.png HTTP/1.1 |
| 10 | 0.062100 | 93.184.216.34 | 192.168.1.100 | HTTP | 1250 | HTTP/1.1 200 OK (image/png) |
| 11 | 0.062200 | 192.168.1.100 | 93.184.216.34 | TCP | 54 | 49152 β 80 [ACK] Seq=247 Ack=1689 Win=62400 |
| 12 | 0.065000 | 192.168.1.100 | 93.184.216.34 | TLS | 256 | Client Hello (SNI: example.com) |
| 13 | 0.072300 | 93.184.216.34 | 192.168.1.100 | TLS | 312 | Server Hello + Certificate |
| 14 | 3.500000 | 192.168.1.100 | 93.184.216.34 | TCP | 54 | 49152 β 80 [FIN, ACK] Seq=247 Ack=1689 Win=62400 |
| 15 | 3.512000 | 93.184.216.34 | 192.168.1.100 | TCP | 54 | 80 β 49152 [FIN, ACK] Seq=1689 Ack=248 Win=64240 |
| 16 | 3.512100 | 192.168.1.100 | 93.184.216.34 | TCP | 54 | 49152 β 80 [ACK] Seq=248 Ack=1690 Win=62400 |
Capture Statistics
Wireshark Features
Display Filters
Filter packets using expressions like `http`, `tcp.port == 80`, or `ip.addr == 192.168.1.1` to isolate specific traffic.
Capture Filters
Use BPF syntax to capture only relevant traffic: `host 93.184.216.34`, `port 80`, or `tcp`.
Follow TCP Stream
Reconstruct the full TCP conversation between two endpoints to see the raw application-layer data exchange.
IO Graphs & Statistics
Visualize throughput, packet rates, protocol hierarchy, and endpoint conversations with built-in graphing tools.
Protocol Hierarchy
View a tree of all detected protocols with packet counts and percentages to understand traffic composition.
Export Objects
Extract files (images, executables, documents) transferred over HTTP, SMB, or other protocols from the capture.
Wireshark Interview Questions
1What is Wireshark and how does it capture packets?
Wireshark is a network protocol analyzer that captures packets by putting the network interface into promiscuous mode, allowing it to see all traffic passing through the interface. It uses libpcap/WinPcap to capture raw frames from the network adapter.
2What is the difference between a display filter and a capture filter?
Capture filters use BPF (Berkeley Packet Filter) syntax and are applied before capture, dropping non-matching packets entirely. Display filters use Wireshark's own expression syntax and only hide packets from viewβthey can be changed after capture without re-capturing.
3How do you analyze a TCP three-way handshake in Wireshark?
Filter by `tcp.stream eq <n>` to isolate a TCP flow. The three-way handshake appears as: (1) Client sends [SYN] with Seq=0, (2) Server responds [SYN, ACK] with Seq=0 and Ack=1, (3) Client sends [ACK] with Seq=1 and Ack=1. This establishes the connection.
4What does the [PSH] flag in a TCP packet mean?
The PSH (Push) flag tells the receiving system to deliver the data to the application immediately without buffering. In Wireshark, [PSH, ACK] packets typically carry application-layer payload like HTTP requests or responses.
5How can you identify a TLS handshake in Wireshark?
Filter by `tls` or `ssl`. The TLS handshake begins with Client Hello (containing supported cipher suites and SNI), followed by Server Hello (selected cipher suite and certificate), then key exchange and finished messages. Look for protocol version 0x0303 (TLS 1.2) or 0x0304 (TLS 1.3).