Wireshark-bugs: [Wireshark-bugs] [Bug 2891] New: wireshark. exe -p switch seems to have no effec
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 22 Sep 2008 13:30:36 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2891

           Summary: wireshark.exe -p switch seems to have no effect to
                    PROMISCUOUS mode
           Product: Wireshark
           Version: 1.0.3
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: poundonu@xxxxxxx


Build Information:
wireshark 1.0.3 (SVN Rev 26134)

Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt 1.4.1, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.

Built using Microsoft Visual C++ 6.0 build 8804
--
wireshark.exe with the "-p" switch to turn OFF promiscuous mode doesn't seem to
have any effect. 

Changing the value of "capture.prom_mode:" in the
%APPDATA%\wireshark\preferences file DOES seem to turn off/on promiscuous mode,
but even if this line in preferences is commented out with "#" (ie. #
capture.prom_mode: FALSE) so that there is no statement in the preferences
file, the "-p" switch still doesn't work.

It seems that "capture.prom_mode:" takes precedence over the -p switch, and
when commented out wireshark.exe defaults to promiscuous mode (ie.
capture.prom_mode: TRUE). 

tshark.exe with "-p" switch works just fine and does NOT exhibit the problem.

This seems to occur in some previous versions of wireshark.exe as well...I
tried v0.99.8 and had the same result.

The problem is problematic when launching wireshark.exe from batch files and
command line, particularly with wireless interfaces where promiscuous mode can
cause issues (or at least require additional config).


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.