Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 5932] Capture filter doesn't work on 1.7.0-SVN-37265

Date: Sat, 21 May 2011 16:26:43 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5932

--- Comment #16 from Jim Aragon <Jim@xxxxxxxxxxxxxxxxx> 2011-05-21 16:26:42 PDT ---
(In reply to comment #12)

> Start wireshark from a shell. Then you should see the debug output in the shell
> (I think it is called cmd in Windows). Can you start capturing the traffic
> using 
> the capture filter and provide the debug output?

I don't know how to direct the conole log output to a file, so uploaded a
screen shot.

> On my machine the output contains (in the middle):

[0]: /Users/tuexen/Documents/wireshark/trunk/dumpcap
> 22:26:51  Capture Dbg  argv[1]: -n
> 22:26:51  Capture Dbg  argv[2]: -i
> 22:26:51  Capture Dbg  argv[3]: en0
> 22:26:51  Capture Dbg  argv[4]: -f
> 22:26:51  Capture Dbg  argv[5]: ip host 192.168.1.61
> 22:26:51  Capture Dbg  argv[6]: -y
> 22:26:51  Capture Dbg  argv[7]: EN10MB
> 22:26:51  Capture Dbg  argv[8]: -Z
> 22:26:51  Capture Dbg  argv[9]: none
> 22:26:51     Main Dbg  Callback: capture prepared
> This is what I'm interested in: Is your capture filter provided to dumpcap (in
> the -f option)?

As you'll see from the screenshot, no it isn't. My capture filter was "icmp".
"-f" and "icmp" are not passed as arguments.

Jim

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