summaryrefslogtreecommitdiff
path: root/tcpdump.1.in
diff options
context:
space:
mode:
authorFrancois-Xavier Le Bail <fx.lebail@yahoo.com>2015-09-17 11:13:21 +0200
committerFrancois-Xavier Le Bail <fx.lebail@yahoo.com>2015-09-17 11:24:07 +0200
commitd128eefdb3aefd55d21f5f065e2dce43e4313998 (patch)
tree9daef6cbe49b9e23ae191b246dd1c536d4a0d073 /tcpdump.1.in
parentf4dd1595652eed7deb50ac52331d01a21a6d45d2 (diff)
downloadtcpdump-d128eefdb3aefd55d21f5f065e2dce43e4313998.tar.gz
Fix the maximum snaplen value in the man page
Diffstat (limited to 'tcpdump.1.in')
-rw-r--r--tcpdump.1.in4
1 files changed, 2 insertions, 2 deletions
diff --git a/tcpdump.1.in b/tcpdump.1.in
index 3f16d89d..0d93d7b8 100644
--- a/tcpdump.1.in
+++ b/tcpdump.1.in
@@ -612,7 +612,7 @@ Print absolute, rather than relative, TCP sequence numbers.
.BI \-\-snapshot\-length= snaplen
.PD
Snarf \fIsnaplen\fP bytes of data from each packet rather than the
-default of 65535 bytes.
+default of 262144 bytes.
Packets truncated because of a limited snapshot
are indicated in the output with ``[|\fIproto\fP]'', where \fIproto\fP
is the name of the protocol level at which the truncation has occurred.
@@ -624,7 +624,7 @@ lost.
You should limit \fIsnaplen\fP to the smallest number that will
capture the protocol information you're interested in.
Setting
-\fIsnaplen\fP to 0 sets it to the default of 65535,
+\fIsnaplen\fP to 0 sets it to the default of 262144,
for backwards compatibility with recent older versions of
.IR tcpdump .
.TP