[Winpcap-bugs] Startup delay related to WinPcap 3.2 and 4.0.1?

[Gianluca Varenni]

  ----- Original Message ----- 
  From: Davis, Bob J - Philadelphia, PA 
  To: winpcap-bugs at winpcap.org 
  Sent: Tuesday, September 04, 2007 10:34 AM
  Subject: [Winpcap-bugs] Startup delay related to WinPcap 3.2 and 4.0.1?


  Hello,

  I have a problem that seems to be related to WinPcap version 3.1 or 4.0 when running Kiwi Syslog Daemon.



  Kiwi starts fine when WinPcap 2.3 is loaded but if WinPcap 3.1 or 4.0 is loaded the Kiwi syslog Daemon hangs on startup.  After 2 minutes all is well.



  WireShark works fine with WinPcap versions 2.3, 3.1 and 4.0 however a problem exists for Kiwi Syslog server when Ver 3.1 or 4.0 is installed.



  Kiwi Syslog runs fine without WinPcap as we are not using the packet spoofing option.



  Can I run WireShark with WinPcap version 2.3?  



Uhm, WinPcap 2.3 might work with the recent versions of Wireshark, but it's a completely unsupported scenario (WinPcap 2.3 by itself is completely unsupported now).



  Have you received any other reports of problems with Kiwi syslog daemon and WinPcap?



Not specific to the kiwi syslog daemon. Does the service start at system boot? Usually the problem is related to the order in which some of the services start. If that is the case, there is a workaround for this involving a couple mods in the registry.



Have a nice day

GV



  I have contacted Kiwi but so far they have been unable to help.



  Thanks for the help,



  Bob Davis 

  US Postal Service 

  National Technical Support







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


  _______________________________________________
  Winpcap-bugs mailing list
  Winpcap-bugs at winpcap.org
  https://www.winpcap.org/mailman/listinfo/winpcap-bugs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-bugs/attachments/20070910/4bde8249/attachment.htm