To see all the details open up the details in the packet details pane, or, if using TShark, add the -V flag to get verbose output. You're capturing these packets and they're dissected right there. Search and Visualize - Exploring the data in detail or in aggregate. Protocol parsing - Parsing out the different network protocols and fields. Packet capture - Recording the packet traffic on a network. Note: I think you'll see the proper ordering is UDP packet first, and in response you'll see the ICMP packetĪs for the question on what you should do to read the contents of the packets, you're already doing that. Any data pipeline for network capture and analysis is composed of several steps: 1. The -z io,stat output will put all the capture file's statistics you're looking for into a single very long line and a '' delimiter. Otherwise the network stack at the destination node wants to inform you that the destination is unreachable, because the (UDP) port is unreachable (or rather, it's closed). Not within tshark -z io,stat (though I wish it could). This succeeds iff there's a proces at the destination node which has opened that UDP port. This packet is used to transport a datagram over IP to the destination node at a specific UDP port. When sending out ICMP echo packets you get a reply, so that's good. Wireshark provides a wide range of network statistics which can be accessed via the Statistics menu. One The use of ping shows you that basic IP networking between the nodes is possible. Select File > Save As or choose an Export option to record the capture. Select the shark fin on the left side of the Wireshark toolbar, press Ctrl+E, or double-click the network. There are other ways to initiate packet capturing. These two observations are only partly related. In the Wireshark Capture Interfaces window, select Start.

Parsing stats from wireshark captures