Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to find the packet loss in Wireshark?

I need to test packet loss for an FTP application. I used the Wireshark packet sniffer, and I got TCP Stream.

How do I find the packet loss using Wireshark?

like image 989
krishnakumar Avatar asked Jun 30 '09 11:06

krishnakumar


People also ask

Can Wireshark detect packet loss?

If you're looking for packet loss in TCP conversations you'll see that Wireshark will mark some packets as "previous segment not captured" followed by "Duplicate ACKs" from the other side, and finally a "retransmission".

How do you check packet loss?

The best way to measure packet loss using ping is to send a large number of pings to the destination and look for failed responses. For instance, if you ping something 50 times and get only 49 responses, you can estimate packet loss at roughly 2% at the moment. Anything over 5% is of concern.

How does Wireshark detect UDP packet loss?

Go to Statistics>Compare, filter by ip.id then click create, if there are any missed ID packets between both files then the results indicate which ip.id packets were lost and then you know which router interface dropped which packet. First, welcome to Wireshark.


1 Answers

Packet loss and other related metrics like bit error rate (BER) can be hard or impossible to empirically see by looking at dumps in Wireshark, depending on what layer you're wanting to look at. And a lot of it is highly dependent on what protocols you're using and what software/firmware is implementing it.

I had this exact experience with Wi-Fi routers, for example. I needed to empirically test the BER of a given Wi-Fi link. But it turns out that 802.11 has a TCP-like CRC based retransmit system that all occurs at the link layer.

So, for example, you may send a UDP packet from Wi-Fi device A to Wi-Fi device B. In transit, a couple of bits get flipped, device B sees that the CRC is wrong and sends a request for retransmit. The packet gets sent again, and again gets corrupted. On the third try, though, the packet gets through fine.

From this, you would hope to see some kind of packet loss metric right? Well, unfortunately no. This whole interchange happens below Wireshark. All it sees is a UDP packet get sent successfully, but take three times as long as normal to get there. (I wound up having to make kernel modifications to send out a notice when link layer CRC errors occurred. It was a mess!)

like image 84
AltF4 Avatar answered Sep 18 '22 05:09

AltF4