Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] Add restrictions to arguments of dumpcap

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Aaron Turner <synfinatic@xxxxxxxxx>
Date: Wed, 6 May 2009 12:40:24 -0700

Personally I think different filters for different interfaces doesn't
make a lot of sense.  I really can't imagine a situation when you'd
need to capture different kinds of packets on different interfaces but
write to a single file.

At least, I think it's fair to say that single filter w/ multiple
interfaces is a more common case then multiple filters & multiple
interfaces.  Ideally the more common case shouldn't require you to
specify the same filter twice.

-- 
Aaron Turner
http://synfin.net/
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
    -- Benjamin Franklin

  • Follow-Ups:
    • Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
      • From: Michael Tüxen
  • References:
    • [Wireshark-dev] Add restrictions to arguments of dumpcap
      • From: Michael Tüxen
  • Prev by Date: Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
  • Next by Date: Re: [Wireshark-dev] Getting wireless GUI to work on Linux
  • Previous by thread: Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
  • Next by thread: Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation