https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3003
Guy Harris <guy@xxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #10 from Guy Harris <guy@xxxxxxxxxxxx> 2008-10-28 17:32:54 PDT ---
(-e is redundant in that case; it only affects output when tcpdump/WinDump is
printing, not when it's saving to the file wth "-w". "-s 0" would cause it not
to cut packets short.)
Yes, so this is either a problem with WinPcap, the driver for your NIC, or the
Windows networking stack.
I'd suggest checking out
http://www.winpcap.org/contact.htm
for help on WinPcap.
The NIC itself is probably not at fault; when it's put into promiscuous mode,
it will obviously accept as input traffic not intended for your machine -
that's the whole point of promiscuous mode. (Is the machine running
Wireshark/WinDump plugged into a span port/mirrored port/monitoring port/etc.
of a managed switch, or into a regular switch, or into a hub? Or is the
network you're on a very old-fashioned Ethernet? Or is it not Ethernet, but
802.11 Wi-Fi? I'm a bit surprised that your machine's even receiving that
traffic.)
Whether those duplicate packets are truly being sent from your machine, or just
being handed up through the networking stack to the WinPcap driver, isn't
clear. In any case, check the page above for help on reporting problems with
WinPcap.
In any case, this isn't a Wireshark bug, so I'm closing this bug.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.