[Winpcap-users] Strange behavior of pcap_next_ex

Jens Munk j.munk at maccor.com
Thu Dec 4 15:04:52 GMT 2008


In my application, I am using pcap_sendpacket to send a raw packagage to 
a networked microcontroller that is within a millisecond or so sending 
another raw package as a reply (old microcontroller -> not IP), and I 
can verify with the WireShark that this is working just fine. However, 
the behavior of pcap_next_ex is not the way I expect. Due to its 
blocking nature I have it sitting in a separate thread, so that should 
be OK, but it doesn't return anything before it sees some kind of an IP 
message like an ARP. Then, however, it keeps returning all the raw 
messages since the last appearance of an IP message.

Is this the way it is supposed to be or am I doing something wrong?

FYI, I have this working using the lower level functions in the 
packet.dll, but I have previously been encouraged to use  wpcap.dll 
instead, so here I am.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: j_munk.vcf
Type: text/x-vcard
Size: 321 bytes
Desc: not available
Url : http://www.winpcap.org/pipermail/winpcap-users/attachments/20081204/924e4389/j_munk.vcf

More information about the Winpcap-users mailing list