[Winpcap-users] Old WinPcap Question

[Gianluca Varenni]

They are in the current version of WinPcap. WinPcap 2.2? I don't have the foggiest idea. They probably were, but also consider that a large number of bugs were fixed since WinPcap 2.2 was released. For sure, if you are using a multiprocessor/multicore machine, WinPcap 2.2 will not work properly there...

Have a nice day
GV
  ----- Original Message ----- 
  From: Rick Anthony 
  To: winpcap-users at winpcap.org 
  Sent: Thursday, May 08, 2008 2:38 PM
  Subject: [Winpcap-users] Old WinPcap Question


  Hi,

   

  I'm trying to debug some old code written around WinPcap 2.2.  I'd rather not update to a newer version if at all possible.

   

  The problem is that pcap_next() sometimes returns a non-NULL packet pointer, but the returned packet header length is 0.  Repeated calls to pcap_next() return the same packet pointer with a header length of 0 and the timestamp no longer increments.

   

  The capture code runs in its own thread and appears correct.  However, I do notice that a separate thread is used to call pcap_sendpacket() with the same pcap descriptor.  Are these calls thread safe?



  I appreciate any help I can get.

   

  Thanks,

  Rick

   



------------------------------------------------------------------------------


  _______________________________________________
  Winpcap-users mailing list
  Winpcap-users at winpcap.org
  https://www.winpcap.org/mailman/listinfo/winpcap-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-users/attachments/20080509/3996bc4c/attachment-0001.htm