Ethereal-dev: Re: [Ethereal-dev] Split the capture-child into it's own program?!?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: LEGO <luis.ontanon@xxxxxxxxx>
Date: Thu, 17 Nov 2005 23:22:58 +0100
> What about the name for this new program? ethdump? ethcapture? ethereal-cap? ethereal-capture? dump2cap? dumpcap?
>
> IMHO dumpcap would be a nice name ...

I do not have good Ideas for a name, but I have thought of an
interface to the caller program (etheral) of this type of capture
agents.

when called without any arguments it should give back to the caller a
parseable list of arguments and the types of those arguments and
whether they are mandatory or not.

$ pcap-capture-agent
-i interface_name<"en0","en1","en2"> -f filter<string,opt>

$ atm-capture-agent
-t tx_interface<"atm0","atm1"> -r rx_interface<"atm0","atm1",opt> -p
vpi<0-65535> -c vci<0-65535> -u uni_nni<"uni","nni">

$ mux-capture-agent
-i interface_list<string> -f filter_list<string,opt>

$ url_fetch-capture-agent
-u url<string>

$ xxx-capture-agent
-x xxx<"x","y">

That way the caller (ethereal) could parse the list of arguments and
create an appropriate capture dialog for whatever agent it is given.

Luis