Ethereal-dev: RE: [Ethereal-dev] Decoding packets while writing to file with te thereal

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

From: "Eichert, Diana" <deicher@xxxxxxxxxx>
Date: Tue, 20 Aug 2002 16:05:37 -0600
> -----Original Message-----
> From: Joerg Mayer [mailto:jmayer@xxxxxxxxx]
> Sent: August 20, 2002 2:32 PM
> To: Eichert, Diana
> Cc: ethereal-dev@xxxxxxxxxxxx
> Subject: Re: [Ethereal-dev] Decoding packets while writing to 
> file with tethereal
SNIP
> I don't want to take away an option that has the effect of completely
> quiet output. The only thing I want is that as long as there aren't
> very good reasons, I don't want option a to influence the behaviour
> of option b, in this instance, I don't like -w to influence whether
> packages are decoded, packet counts shown etc. As I didn't want to
> change the behaviour of existing flags, I chose -Q. Maybe something
> like -q[scdv] s: silent, c: count, d:decode v:verbose decode would
> make more sense. OK, remove that maybe :-) 
> 
>   Ciao
>         Jörg

Hmmm, I had been using tcpdump for years before installing Ethereal, 
which came with this great tool tethereal.  In some ways tethereal 
works as tcpdump(ex: capture filter language), and sometimes 
differently(ex: default snap length, quietness of -w).  Tcpdump is 
quiet when capturing with the "-w" switch invoked.  I needed the 
quietness of tcpdump, so I modified a local copy, then posted the 
diff's on the user list.

I've always thought that tethereal should use tcpdump's default 
operation for it's defaults and give tethereal a superset to support 
it's additional features.  This would allow me to interchange the use 
of tethereal/tcpdump, depending on it's availability, in scripts with 
no modification.  However that's only my opinion.  I think the people 
that have written it can have it operate anyway they please.

g,day

diana