http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1201
jmayer@xxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
------- Comment #5 from jmayer@xxxxxxxxx 2006-11-04 18:12 GMT -------
OK, just to explain Ulfs answer a bit better:
the capturing library is only packaged by wireshark, but we do not code it.
Ulf assumes (as do I) that the problem is in the capture part, so it will be
in winpcap and not in the wireshark source code. That means, that we cannot
change the source of wireshark to make your problem go away.
So please repeat the test with windump (the capture application that is
part of the winpcap package). If the problem still exists, then this is indeed
a wireshark bug, otherwise it is a winpcap bug that must be reported to
the winpcap authors.
I'm closing it as invalid. Please feel free to repoen it in case the problem
only occurrs with wireshark but not with windump.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.