[Winpcap-users] ANNOUNCE: WinPcap 4.0 beta2 has been released

[Alto Speckhardt]

Guten Morgen,

Sorry, it took me a while to get around to continue testing.


GV> By crashes you mean blue screen or application crashes?
GV> By freeze you mean the complete OS freezing (i.e. you need to reboot).
GV> Right?

Actually, I meant the same by both expressions: Windows ceasing to
respond, no more mouse movement, no reaction to keyboard toggles (caps
etc.) So yes, your definition for "freeze" is correct, while my use of
"crash" should have been omitted. ;-)

BTW: The "last exit", Ctrl-Scrol-Scroll to terminate Windows the hard
way still works, but that is the only thing.


GV> Is Windump crashing/freezing in the same way?

No, to my surprise it didn't. I started it maybe five times in a row
and it worked each time, wheras Wireshark, started right afterward,
caused a system freeze after the third "start capture" (the two first
start/stop captures worked all right, packets were shown.)

Is it normal that Windump just sits there at first, displaying

<timestamp> IP

for a few seconds before it continues like

<timestamp> IP <from> <to>
<timestamp> IP <from> <to>
<timestamp> IP <from> <to>
[...]


and that it lags a little behind the actual traffic?


Regards,
Alto



GV> ----- Original Message ----- 
GV> From: "Alto Speckhardt" <1603 at gmx.de>
GV> To: "Gianluca Varenni" <winpcap-users at winpcap.org>
GV> Sent: Saturday, October 21, 2006 5:34 PM
GV> Subject: Re: [Winpcap-users] ANNOUNCE: WinPcap 4.0 beta2 has been released
GV> Hi,


GV>> WinPcap 4.0 beta2 is available as of today in the download section of
GV>> the WinPcap website, http://www.winpcap.org/install/.

GV> Taking the occasion, I performed some new test with Etherall/Wireshark
GV> to see whether my crash-problems would be gone with this version of
GV> WinPCap.

GV> In short: They are not. But they've changed.

GV> I installed WinPCap v4/b2 over v3.1/b4 (no reboot) and tried the
GV> already installed Ethereal v0.10.14. As usual, the first capture
GV> start-stop worked. On the second, however, the program failed to show
GV> any packets, and then wasn't able to stop at all (Stop-button still
GV> enabled, Start-button hidden). But it didn't freeze as before.

GV> So I thought that maybe the error that I'm seeing would be caught in
GV> the new version and would no longer lead to the crashs. So I updated
GV> Ethereall to Wireshark v0.99.3. On starting this one no interfaces
GV> were detected. Which was not all that surprising since I still had not
GV> rebooted after updating WinPCap.

GV> After rebooting I startet Wireshark again: First capture start-stop,
GV> ok. Second start - Freeze.

GV> I then installed WinPCap v3.1/beta 4 again and again started
GV> Wireshark. Surprise: now it worked.



GV> I therefore dare say that the problem is not with Ethereal/Wireshark
GV> but indeed with WinPCap itself. I sure could use some help in
GV> troubleshooting.





-- 
MfG,
 Alto                            mailto:Alto at treadstone79.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 505 bytes
Desc: not available
Url : http://www.winpcap.org/pipermail/winpcap-users/attachments/20061029/4804bf10/attachment.pgp