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

From: Michael Tüxen <Michael.Tuexen@xxxxxxxxxxxxxxxxx>
Date: Thu, 7 May 2009 17:32:22 -0400

On May 7, 2009, at 5:16 PM, Guy Harris wrote:

On May 7, 2009, at 1:50 PM, Sake Blok wrote:

Make every CLO have effect on *all* interfaces until an interface is
specified, then make all following CLO's have an effect on *only*
the last
listed interface.

That sounds good to me.

This is what I had initially in mind. However, ordering of the
arguments is then important, as some dislike. However, I like
this ordering related stuff more than the comma separated -i args...

Presumably a "global" option is overridden by per-interface options,
e.g.:

	dumpcap -s 96 -i en0 -i en1 -y IEEE802_11_RADIO_AVS -s 128

would capture on en0 with a snapshot size of 96 and the default link-
layer type and on en1 with a snapshot size of 128 and a link-layer
type of IEEE802_11_RADIO_AVS.

What happens with multiple -i options and the -L option?  Does it
list, for each interface, the available link-layer type values, or
does it fail?

I would just fail them. I actually would require an -n option before
the second -i. We will only support capturing from multiple interfaces
when using PCAPNG...

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe