On 08/21/2013 01:19 AM, Kevin Branch wrote:
With netsniff-ng 0.5.8-rc2+, when I run the below packet capture session, the
output seems to imply that 64K of memory is being allocated per frame, which
does not look like what I want since my interface MTU is only 1500. This
appears to be severely limiting the number of frames I can fit into my packet
capture ring.
[root@nids-sen ttt]# netsniff-ng --in dmz -s --out dump.cap -S 256MiB -V
RX: 256.00 MiB, 4096 Frames, each 65536 Byte allocated
Running! Hang up with ^C!
Should I do something to explicitly disable jumbo frames support?
Nope, the capture-only setting of netsniff-ng uses TPACKET_V3, where there is
no such restriction of static frame slot sizes as in TPACKET_V2 where e.g.
each frame is of max size 4096 usually. Frames are written to the ring buffer in
a continuous way. It uses the same API in netsniff-ng and therefore just prints
the same setting. So, you don't need to do anything explicitly here.
But I agree with you that we should change the verbose output of that line in
this case. Will push a patch in a moment.
--
You received this message because you are subscribed to the Google Groups
"netsniff-ng" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
