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?
Kevin
--
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.
