Hello Joerg,
Thats a great idea, also it could assume that STDIN = pcap format,
since thats the native packaging.
Joe.
--
__o _~o __o
"Know your Network" `\<, `\<, `\<,
______________________________________(*)/_(*)__(*)/_(*)__(*)/_(*)________
Im a 21st Century Digital Boy ... I aint got a life, but I got lotsa toys.
*************** Joe Elliott joe@xxxxxxxxx AOL:xqos ********************
- NetContExt - sniffer trace forensics - tcp follow stream analysis -
- Extract data files and Images from tcpdump & ethereal packet payloads -
Inetd.Com Network analysis solutions http://www.inetd.com
--------------------------------------------------------------------------
On Wed, 19 Oct 2005, Joerg Mayer wrote:
> Date: Wed, 19 Oct 2005 18:53:42 +0200
> From: Joerg Mayer <jmayer@xxxxxxxxx>
> Reply-To: Ethereal user support <ethereal-users@xxxxxxxxxxxx>
> To: Ethereal user support <ethereal-users@xxxxxxxxxxxx>
> Subject: Re: [Ethereal-users] tethereal performance questions
>
> On Wed, Oct 19, 2005 at 12:32:03AM -0700, Guy Harris wrote:
> > >Can the developers put the '-r -' functionality in?
> >
> > Not very conveniently. Tcpdump reads fewer types of capture files than
> > does Tethereal; Tethereal's capture-file-reading library (the same one
> > as Ethereal) determines the file type (and some other characteristics of
> > the file) by trying to read the file multiple times. That's done by
> > seeking back to the beginning of the file and reading; that doesn't work
> > on pipes.
>
> There is another way to do this quite easily: When running from a pipe,
> *force* the user to specify the input file format (just recycle the -F
> option?)
>
> Ciao
> Joerg
>