[ previous ] [ next ] [ threads ]
 
 From:  Cedric Jeanneret <cjeanneret at internux dot ch>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] [Request] tcpdump
 Date:  Mon, 20 Apr 2009 16:00:18 +0200
Hmm, interesting, yes.

Maybe we can store it in RAM and let choose how to catch it back (mail, ddl, scp to a server, ...) ?
As tcpdump has a small output [even with -vvv, it's not that big], I guess it can be stored in ram
even on small box

In any case, that can really be an improvement I think.

Regards,

C. Jeanneret




On Mon, 20 Apr 2009 15:03:40 +0200
Silvan Michael Gebhardt <pcdog at pcdog dot ch> wrote:

> the problem is the storage,
> 
> 
> but I think one could solve it by just creating a file that gets  
> downloaded immediately on the browser... so as soon as we have the  
> tcpdump started, you would send it out as a file with php instead of  
> tcpdumping to a real file (by e.g using a socket as a file?)
> 
> is that possible, manuel?
> 
> 
> 
> 
> lg
> Silvan
> 
> 
> 
> 
> Am 20.04.2009 um 15:01 schrieb Cedric Jeanneret:
> 
> > Hello,
> >
> > In order to performe some tests on my network, and to find which  
> > ports are important to NAT, I'd like to use a tcpdump from my Alix  
> > box, which has the latest [working] beta m0n0...
> >
> > Is it possible to have an interface for tcpdump? or even tcpdump and  
> > an ssh access... it can really be useful for net debugging,  
> > especially for such an important device...
> >
> > Regards,
> >
> > C. Jeanneret
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> >
>