[Click] ToDump with SNAPLEN 0 problems

[Eddie Kohler]

Marcel Poisot wrote:
> I want to capture entire packets no matter how large they are, so I set 
> the SNAPLEN field to 0. I tried the different syntaxes just to make sure:
>     ToDump( HTTP.dump, 0, ENCAP IP )
>     ToDump( HTTP.dump, SNAPLEN 0, ENCAP IP )
> 
> However, when I try to view the dump with tcpdump it reports:
>     tcpdump: snaplen of 0 rejects all packets
> 
> Ethereal agrees that there isn't much in the dump.  "48 bytes on wire, 0 
> captured".
> 
> Moreover, when the first packet is received, the router prints the line:
>     ToDump(HTTP.dump): Success
> 
> 
> If I supply a number (like 3000) for SNAPLEN, or just use the default 
> value, tcpdump reads the file just fine and there is no "Success" print 
> statement.
> 
> Suggestions?

Whoops!  This was a bug on our part.  CVS now treats SNAPLEN 0 as equivalent to 
SNAPLEN 0xFFFFFFFF, which works.  In the meantime, you can just say SNAPLEN 
0xFFFFFFFF.  Thanks!

Eddie



> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click