Ping Traces and Wireshark captures

edit

These two observations are only partly related.

One; The use of ping shows you that basic IP networking between the nodes is possible. When sending out ICMP echo packets you get a reply, so that's good.

Two; Then you send out a UDP packet. This packet is used to transport a datagram over IP to the destination node at a specific UDP port. This succeeds iff there's a proces at the destination node which has opened that UDP port. 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). That is what that ICMP packet is for.

Note: I think you'll see the proper ordering is UDP packet first, and in response you'll see the ICMP packet

As for the question on what you should do to read the contents of the packets, you're already doing that. You're capturing these packets and they're dissected right there. 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.

The contents posted are not your pings. 10.10.100.254----10.10.100.1-------------ICMP----------------70-----------------Destination Unreachable(port unreachable), you have to look at the packet detail for more information. It could be the because of the subsequent packet 10.10.100.1 trying to reach 10.10.100.254:192.

10.10.100.1-------10.10.100.254----------UDP-----------------46-----------------55180 -> 192 Len = 4 is trying to send a packet to 10.10.100.254:192

To see only all traffic between the two addresses start building a complex display filter using ip.addr==xx.xx.xx.xx. The complex display filter will narrow the display packets to only the traffic you are interested in.