Bug 9945 - tcpdump and promiscuous mode
tcpdump and promiscuous mode
Status: CLOSED DUPLICATE of bug 6464
Product: Red Hat Linux
Classification: Retired
Component: tcpdump (Show other bugs)
6.2
All Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-03-03 18:54 EST by Gordon Messmer
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-03-04 12:33:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Gordon Messmer 2000-03-03 18:54:57 EST
tcpdump doesn't seem to put an interface into promiscuous mode unless you
use the -p flag.  However, the man page for tcpdump says:

-p     _Don't_  put  the  interface  into promiscuous mode.

Only after using the '-p' flag does the dmesg report that the interface was
put into promiscuous mode.

Further, even whether the device is in promiscuous mode or not, tcpdump
only dumps traffic that comes to a local interface (or is broadcast). This
behavior is consistant among libpcap apps (ngrep, etherape), so maybe this
bug is kernel related?? (running kernel 2.2.15-pre2)
Comment 1 Jeff Johnson 2000-03-04 12:33:59 EST
The man page is wrong and will be fixed.

*** This bug has been marked as a duplicate of 6464 ***

Note You need to log in before you can comment on or make changes to this bug.