[Winpcap-users] EXT : Confusion: How can we identify where the packet is lost?

[Black, Mike (IS)]

If you're using UDP (also know as Unreliable Data Protocol) you can most definitely lose packets.

It's unlikely you are losing them on the sending side. Most likely lost in the wire due to collisions or the receiving side not clearing the queue fast enough.


Try TCP packets instead which are much more reliable (though the TCP protocol is not guaranteed either due to connection resets and such).


Michael D. Black
Senior Scientist
Analytics, Production and Services
Northrop Grumman Information Systems

________________________________
From: winpcap-users-bounces at winpcap.org <winpcap-users-bounces at winpcap.org> on behalf of ??? <fan.tingdong at gmail.com>
Sent: Sunday, September 7, 2014 6:59 AM
To: winpcap-users
Subject: EXT :[Winpcap-users] Confusion: How can we identify where the packet is lost?

Dear all,

I am writing a software program(with support from winpcap) which tests if a device could send packets continously to my laptop without loss of packets.

The sending part send packets with four bits for counter , and the receiving part check if there is incontinuity of the counts, as shown in the picture below.  Winpcap driver was working in PACKET_MODE_CAPT mode(mode=PACKET_MODE_CAPT). The Receing part found there were lost of packets when I was testing the software.

[cid:3C384F9F at C69EC16A.A5480C54.bmp]

Then I got a confusion: Where were the packets lost? The receiving part(my laptop) did not receive the packets successfully, or the sending part failed sending the packets?

Hopefully anyone could provide any hits.  Thank you all in advance.

Best regards,

Fan Tingdong
User and Fans of Winpcap


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20150604/acb467d8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3C384F9F at C69EC16A.A5480C54.bmp
Type: application/octet-stream
Size: 196238 bytes
Desc: 3C384F9F at C69EC16A.A5480C54.bmp
URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20150604/acb467d8/attachment-0001.obj>