diff options
| author | Daniel Borkmann <dborkman@redhat.com> | 2013-08-21 09:59:06 +0200 |
|---|---|---|
| committer | Daniel Borkmann <dborkman@redhat.com> | 2013-08-21 09:59:06 +0200 |
| commit | 74a4979266860005c0013cdc86208be204cddd1d (patch) | |
| tree | 0ab9f9b67f2bbfae9732aab77431d807635dd290 /astraceroute | |
| parent | 2f4f8cda836e9d1a34e13e8c3e0683d75fcd9ad4 (diff) | |
ring_{rx,tx}: verbose: output version and v3 specific info
Kevin says:
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.
As TPACKET_V3 is used in capturing to pcap files, frames are written
continuously to the ring, thus the above will give a wrong impression
to the user. Therefore, output such information in verbose mode
differently when TPACKET_V3 is being used, as it works block-wise.
Reported-by: Kevin Branch <branchnetconsulting@gmail.com>
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Diffstat (limited to 'astraceroute')
0 files changed, 0 insertions, 0 deletions