Ethereal-dev: Re: [Ethereal-dev] Idea for ethereal

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

From: "Ronnie Sahlberg" <ronnie_sahlberg@xxxxxxxxxxxxxx>
Date: Thu, 8 Apr 2004 14:46:09 +1000
what i mean is, this exact daemon that you describe already exist.
ethereal already contain the client/server code to hook up to that daemon to
do live captures.
it takes as little resources as possible.
it is dormant when no one is connected to it.

it already exists and is a 100% match to your requirements as you described
them.


----- Original Message ----- 
From: "Ronnie Sahlberg"
Sent: Thursday, April 08, 2004 2:42 PM
Subject: Re: [Ethereal-dev] Idea for ethereal


> It is part of the ethereal gui.
>
> Run ethereal locally on your desktop,  when starting a capture type in
> rpcap://10.1.2.3/eth0
> or something similar where you select which interface to capture from.
> the capture will then be performed on the remote host 10.1.2.3 on that
hosts
> interface eth0 and the pacekts will be transferred across the entwork to
> your ethereal session as if you were capturing locally.
>
>
>
>
> ----- Original Message ----- 
> From: "Don Lafontaine"
> Sent: Thursday, April 08, 2004 2:27 PM
> Subject: Re: [Ethereal-dev] Idea for ethereal
>
>
> > Thanks,  I kinda already have a tool that does it.  Just throwing out an
> > idea.  Anyone can run remote captures,  it's just handier to have it
> > part of the ethereal GUI.
> >
> > Don.
> >
> > Ronnie Sahlberg wrote:
> >
> > >1, Goto winpcap website.
> > >
> > >2, download the rpcap.exe daemon
> > >
> > >3, do remote captures.
> > >
> > >----- Original Message ----- 
> > >From: "Don Lafontaine"
> > >Sent: Thursday, April 08, 2004 2:11 PM
> > >Subject: [Ethereal-dev] Idea for ethereal
> > >
> > >
> > >
> > >
> > >>Hi folks
> > >>
> > >>It would be a real handy addition to add client/server capture
> > >>functionality to ethereal.
> > >>
> > >>Write a small footprint capture daemon/service that can be started by
a
> > >>remote ethereal client.  It captures packets until told to stop.  At
> > >>that point, the client (ethereal) downloads the captured data and
> > >>presents it for the user to peruse.  This daemon/service will remain
> > >>dormant until called into service,  it needs to use as little
resources
> > >>as possible when not in use.  One little form can list all the
available
> > >>daemon/services and the user can click one or more. If more than one
are
> > >>chosen,  ethereal can be made to match up the packets so you can see
> > >>both sides of the conversations from each side of the wire. This will
> > >>give you latency/delay/drops if you match them up properly.
> > >>
> > >>Just an idle thought,  what do you think?
> > >>
> > >>Don Lafontaine
> > >>
> > >>_______________________________________________
> > >>Ethereal-dev mailing list
> > >>Ethereal-dev@xxxxxxxxxxxx
> > >>http://www.ethereal.com/mailman/listinfo/ethereal-dev
> > >>
> > >>
> > >>
> > >
> > >_______________________________________________
> > >Ethereal-dev mailing list
> > >Ethereal-dev@xxxxxxxxxxxx
> > >http://www.ethereal.com/mailman/listinfo/ethereal-dev
> > >
> > >
> >
> > _______________________________________________
> > Ethereal-dev mailing list
> > Ethereal-dev@xxxxxxxxxxxx
> > http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev