https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5932
--- Comment #22 from Jim Aragon <Jim@xxxxxxxxxxxxxxxxx> 2011-05-21 17:04:28 PDT ---
(In reply to comment #18)
> (That seems a bit clunky. Perhaps there should be a command-line option to
> start up Wireshark with the "Capture Options" dialog open?)
It wouldn't hurt to have such an option, but most of the time I don't want a
capture filter, so wouldn't want the Capture Options dialog to pop open. When I
discovered this bug, I had launched Wireshark with my usual options (-k -c
20000 -i 1) and didn't want a capture filter. It was only after observing the
traffic that was being captured that I decided to apply a capture filter in
order to focus on particular traffic.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
