https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7867
--- Comment #1 from Guy Harris <guy@xxxxxxxxxxxx> 2012-10-16 14:54:21 PDT ---
One other capture packet program is WinDump:
http://www.winpcap.org/windump/default.htm
It's a command-line tool. If you can reproduce the problem with it, it's not a
problem with Wireshark, it's a problem with WinPcap, which is the packet
capture mechanism that both Wireshark and WinDump use (and that some other
programs also use).
(WinPcap is libpcap-for-Windows; libpcap is a library that runs atop the
underlying capture mechanisms in many UN*Xes, so a lot of packet analyzers
written for UN*X, such as tcpdump and Wireshark use it. Windows doesn't have
an underlying capture mechanism, so WinPcap has to provide its own driver to
provide one; it connects to the underlying Windows networking stack in a
fashion different from the fashion in which NetMon's driver does, which may be
the source of the problem here.)
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
