Introduce --time-stamp-precision

[tcpdump] / tcpdump.1.in

diff --git a/tcpdump.1.in b/tcpdump.1.in
index 6a4354a05b0d46a295606b7c440114ed84dc4703..3cceb4683fba647570e997f6d6fa701db9f2fb6f 100644 (file)
--- a/tcpdump.1.in
+++ b/tcpdump.1.in
@@ -1,5 +1,3 @@
-.\" @(#) $Header: /tcpdump/master/tcpdump/tcpdump.1.in,v 1.2 2008-11-09 23:35:03 mcr Exp $ (LBL)
-.\"

 .\"    $NetBSD: tcpdump.8,v 1.9 2003/03/31 00:18:17 perry Exp $
 .\"
 .\" Copyright (c) 1987, 1988, 1989, 1990, 1991, 1992, 1994, 1995, 1996, 1997
 .\"    $NetBSD: tcpdump.8,v 1.9 2003/03/31 00:18:17 perry Exp $
 .\"
 .\" Copyright (c) 1987, 1988, 1989, 1990, 1991, 1992, 1994, 1995, 1996, 1997


@@ -22,14 +20,14 @@
 .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
 .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
 .\"
 .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
 .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
 .\"

-.TH TCPDUMP 1  "05 March 2009"
+.TH TCPDUMP 1  "6 May 2014"

 .SH NAME
 tcpdump \- dump traffic on a network
 .SH SYNOPSIS
 .na
 .B tcpdump
 [
 .SH NAME
 tcpdump \- dump traffic on a network
 .SH SYNOPSIS
 .na
 .B tcpdump
 [

-.B \-AdDefIKlLnNOpqRStuUvxX
+.B \-AbdDefhHIJKlLnNOpqRStuUvxX

 ] [
 .B \-B
 .I buffer_size
 ] [
 .B \-B
 .I buffer_size


@@ -56,6 +54,10 @@ tcpdump \- dump traffic on a network
 .I interface
 ]
 [
 .I interface
 ]
 [

+.B \-j
+.I tstamp_type
+]
+[

 .B \-m
 .I module
 ]
 .B \-m
 .I module
 ]


@@ -66,10 +68,22 @@ tcpdump \- dump traffic on a network
 .br
 .ti +8
 [
 .br
 .ti +8
 [

+.B \-\-number
+]
+[
+.B \-Q
+.I in|out|inout
+]
+.ti +8
+[

 .B \-r
 .I file
 ]
 [
 .B \-r
 .I file
 ]
 [

+.B \-V
+.I file
+]
+[

 .B \-s
 .I snaplen
 ]
 .B \-s
 .I snaplen
 ]


@@ -109,6 +123,9 @@ tcpdump \- dump traffic on a network
 ]
 .ti +8
 [
 ]
 .ti +8
 [

+.B \-\-version
+]
+[

 .I expression
 ]
 .br
 .I expression
 ]
 .br


@@ -123,8 +140,10 @@ flag, which causes it to save the packet data to a file for later
 analysis, and/or with the
 .B \-r
 flag, which causes it to read from a saved packet file rather than to
 analysis, and/or with the
 .B \-r
 flag, which causes it to read from a saved packet file rather than to

-read packets from a network interface.  In all cases, only packets that
-match
+read packets from a network interface.  It can also be run with the
+.B \-V
+flag, which causes it to read a list of saved packet files. In all cases,
+only packets that match

 .I expression
 will be processed by
 .IR tcpdump .
 .I expression
 will be processed by
 .IR tcpdump .


@@ -191,13 +210,22 @@ special privileges.
 Print each packet (minus its link level header) in ASCII.  Handy for
 capturing web pages.
 .TP
 Print each packet (minus its link level header) in ASCII.  Handy for
 capturing web pages.
 .TP

-.B \-B
-Set the operating system capture buffer size to \fIbuffer_size\fP.
+.B \-b
+Print the AS number in BGP packets in ASDOT notation rather than ASPLAIN
+notation.

 .TP
 .TP

-.B \-c
+.BI \-B " buffer_size"
+.PD 0
+.TP
+.BI \-\-buffer\-size= buffer_size
+.PD
+Set the operating system capture buffer size to \fIbuffer_size\fP, in
+units of KiB (1024 bytes).
+.TP
+.BI \-c " count"

 Exit after receiving \fIcount\fP packets.
 .TP
 Exit after receiving \fIcount\fP packets.
 .TP

-.B \-C
+.BI \-C " file_size"

 Before writing a raw packet to a savefile, check whether the file is
 currently larger than \fIfile_size\fP and, if so, close the current
 savefile and open a new one.  Savefiles after the first savefile will
 Before writing a raw packet to a savefile, check whether the file is
 currently larger than \fIfile_size\fP and, if so, close the current
 savefile and open a new one.  Savefiles after the first savefile will


@@ -220,6 +248,10 @@ program fragment.
 Dump packet-matching code as decimal numbers (preceded with a count).
 .TP
 .B \-D
 Dump packet-matching code as decimal numbers (preceded with a count).
 .TP
 .B \-D

+.PD 0
+.TP
+.B \-\-list\-interfaces
+.PD

 Print the list of the network interfaces available on the system and on
 which
 .I tcpdump
 Print the list of the network interfaces available on the system and on
 which
 .I tcpdump


@@ -247,12 +279,14 @@ that lacks the
 function.
 .TP
 .B \-e
 function.
 .TP
 .B \-e

-Print the link-level header on each dump line.
+Print the link-level header on each dump line.  This can be used, for
+example, to print MAC layer addresses for protocols such as Ethernet and
+IEEE 802.11.

 .TP
 .B \-E
 Use \fIspi@ipaddr algo:secret\fP for decrypting IPsec ESP packets that
 are addressed to \fIaddr\fP and contain Security Parameter Index value
 .TP
 .B \-E
 Use \fIspi@ipaddr algo:secret\fP for decrypting IPsec ESP packets that
 are addressed to \fIaddr\fP and contain Security Parameter Index value

-\fIspi\fP. This combination may be repeated with comma or newline seperation.
+\fIspi\fP. This combination may be repeated with comma or newline separation.

 .IP
 Note that setting the secret for IPv4 ESP packets is supported at this time.
 .IP
 .IP
 Note that setting the secret for IPv4 ESP packets is supported at this time.
 .IP


@@ -267,8 +301,8 @@ The default is \fBdes-cbc\fP.
 The ability to decrypt packets is only present if \fItcpdump\fP was compiled
 with cryptography enabled.
 .IP
 The ability to decrypt packets is only present if \fItcpdump\fP was compiled
 with cryptography enabled.
 .IP

-\fIsecret\fP is the ASCII text for ESP secret key. 
-If preceeded by 0x, then a hex value will be read.
+\fIsecret\fP is the ASCII text for ESP secret key.
+If preceded by 0x, then a hex value will be read.

 .IP
 The option assumes RFC2406 ESP, not RFC1827 ESP.
 The option is only for debugging purposes, and
 .IP
 The option assumes RFC2406 ESP, not RFC1827 ESP.
 The option is only for debugging purposes, and


@@ -279,7 +313,7 @@ you make it visible to others, via
 and other occasions.
 .IP
 In addition to the above syntax, the syntax \fIfile name\fP may be used
 and other occasions.
 .IP
 In addition to the above syntax, the syntax \fIfile name\fP may be used

-to have tcpdump read the provided file in. The file is opened upon 
+to have tcpdump read the provided file in. The file is opened upon

 receiving the first ESP packet, so any special permissions that tcpdump
 may have been given should already have been given up.
 .TP
 receiving the first ESP packet, so any special permissions that tcpdump
 may have been given should already have been given up.
 .TP


@@ -297,11 +331,11 @@ because the capture is being done on the Linux "any" interface, which
 can capture on more than one interface, this option will not work
 correctly.
 .TP
 can capture on more than one interface, this option will not work
 correctly.
 .TP

-.B \-F
+.BI \-F " file"

 Use \fIfile\fP as input for the filter expression.
 An additional expression given on the command line is ignored.
 .TP
 Use \fIfile\fP as input for the filter expression.
 An additional expression given on the command line is ignored.
 .TP

-.B \-G
+.BI \-G " rotate_seconds"

 If specified, rotates the dump file specified with the
 .B \-w
 option every \fIrotate_seconds\fP seconds.
 If specified, rotates the dump file specified with the
 .B \-w
 option every \fIrotate_seconds\fP seconds.


@@ -315,11 +349,30 @@ If used in conjunction with the
 .B \-C
 option, filenames will take the form of `\fIfile\fP<count>'.
 .TP
 .B \-C
 option, filenames will take the form of `\fIfile\fP<count>'.
 .TP

-.B \-i
+.B \-h
+.PD 0
+.TP
+.B \-\-help
+.PD
+Print the tcpdump and libpcap version strings, print a usage message,
+and exit.
+.TP
+.B \-\-version
+.PD
+Print the tcpdump and libpcap version strings and exit.
+.TP
+.B \-H
+Attempt to detect 802.11s draft mesh headers.
+.TP
+.BI \-i " interface"
+.PD 0
+.TP
+.BI \-\-interface= interface
+.PD

 Listen on \fIinterface\fP.
 If unspecified, \fItcpdump\fP searches the system interface list for the
 Listen on \fIinterface\fP.
 If unspecified, \fItcpdump\fP searches the system interface list for the

-lowest numbered, configured up interface (excluding loopback).
-Ties are broken by choosing the earliest match.
+lowest numbered, configured up interface (excluding loopback), which may turn
+out to be, for example, ``eth0''.

 .IP
 On Linux systems with 2.2 or later kernels, an
 .I interface
 .IP
 On Linux systems with 2.2 or later kernels, an
 .I interface


@@ -335,6 +388,10 @@ used as the
 argument.
 .TP
 .B \-I
 argument.
 .TP
 .B \-I

+.PD 0
+.TP
+.B \-\-monitor\-mode
+.PD

 Put the interface in "monitor mode"; this is supported only on IEEE
 802.11 Wi-Fi interfaces, and supported only on some operating systems.
 .IP
 Put the interface in "monitor mode"; this is supported only on IEEE
 802.11 Wi-Fi interfaces, and supported only on some operating systems.
 .IP


@@ -355,7 +412,40 @@ monitor mode will be shown; if
 is specified, only those link-layer types available when in monitor mode
 will be shown.
 .TP
 is specified, only those link-layer types available when in monitor mode
 will be shown.
 .TP

+.BI \-j " tstamp_type"
+.PD 0
+.TP
+.BI \-\-time\-stamp\-type= tstamp_type
+.PD
+Set the time stamp type for the capture to \fItstamp_type\fP.  The names
+to use for the time stamp types are given in
+.BR pcap-tstamp (@MAN_MISC_INFO@);
+not all the types listed there will necessarily be valid for any given
+interface.
+.TP
+.B \-J
+.PD 0
+.TP
+.B \-\-list\-time\-stamp\-types
+.PD
+List the supported time stamp types for the interface and exit.  If the
+time stamp type cannot be set for the interface, no time stamp types are
+listed.
+.TP
+.BI \-\-time\-stamp\-precision= tstamp_precision
+.PD
+Set the time stamp precision for the capture to
+\fItstamp_precision\fP. Currently supported are microseconds and
+nanoseconds. Note that availability of high precision time stamps (nanoseconds)
+and their actual accuracy is platform and HW dependent. Also note that when
+writing captures to the savefile, distinct magic number is used to distinguish
+savefiles which contains time stamps in nanoseconds.
+.TP

 .B \-K
 .B \-K

+.PD 0
+.TP
+.B \-\-dont\-verify\-checksums
+.PD

 Don't attempt to verify IP, TCP, or UDP checksums.  This is useful for
 interfaces that perform some or all of those checksum calculation in
 hardware; otherwise, all outgoing TCP checksums will be flagged as bad.
 Don't attempt to verify IP, TCP, or UDP checksums.  This is useful for
 interfaces that perform some or all of those checksum calculation in
 hardware; otherwise, all outgoing TCP checksums will be flagged as bad.


@@ -365,11 +455,43 @@ Make stdout line buffered.
 Useful if you want to see the data
 while capturing it.
 E.g.,
 Useful if you want to see the data
 while capturing it.
 E.g.,

-.br
-``tcpdump\ \ \-l\ \ |\ \ tee dat'' or
-``tcpdump\ \ \-l \ \ > dat\ \ &\ \ tail\ \ \-f\ \ dat''.
+.IP
+.RS
+.RS
+.nf
+\fBtcpdump \-l | tee dat\fP
+.fi
+.RE
+.RE
+.IP
+or
+.IP
+.RS
+.RS
+.nf
+\fBtcpdump \-l > dat & tail \-f dat\fP
+.fi
+.RE
+.RE
+.IP
+Note that on Windows,``line buffered'' means ``unbuffered'', so that
+WinDump will write each character individually if
+.B \-l
+is specified.
+.IP
+.B \-U
+is similar to
+.B \-l
+in its behavior, but it will cause output to be ``packet-buffered'', so
+that the output is written to stdout at the end of each packet rather
+than at the end of each line; this is buffered on all platforms,
+including Windows.

 .TP
 .B \-L
 .TP
 .B \-L

+.PD 0
+.TP
+.B \-\-list\-data\-link\-types
+.PD

 List the known data link types for the interface, in the specified mode,
 and exit.  The list of known data link types may be dependent on the
 specified mode; for example, on some platforms, a Wi-Fi interface might
 List the known data link types for the interface, in the specified mode,
 and exit.  The list of known data link types may be dependent on the
 specified mode; for example, on some platforms, a Wi-Fi interface might


@@ -380,12 +502,12 @@ and another set of data link types when in monitor mode (for example, it
 might support 802.11 headers, or 802.11 headers with radio information,
 only in monitor mode).
 .TP
 might support 802.11 headers, or 802.11 headers with radio information,
 only in monitor mode).
 .TP

-.B \-m
+.BI \-m " module"

 Load SMI MIB module definitions from file \fImodule\fR.
 This option
 can be used several times to load several MIB modules into \fItcpdump\fP.
 .TP
 Load SMI MIB module definitions from file \fImodule\fR.
 This option
 can be used several times to load several MIB modules into \fItcpdump\fP.
 .TP

-.B \-M
+.BI \-M " secret"

 Use \fIsecret\fP as a shared secret for validating the digests found in
 TCP segments with the TCP-MD5 option (RFC 2385), if present.
 .TP
 Use \fIsecret\fP as a shared secret for validating the digests found in
 TCP segments with the TCP-MD5 option (RFC 2385), if present.
 .TP


@@ -398,18 +520,38 @@ E.g.,
 if you give this flag then \fItcpdump\fP will print ``nic''
 instead of ``nic.ddn.mil''.
 .TP
 if you give this flag then \fItcpdump\fP will print ``nic''
 instead of ``nic.ddn.mil''.
 .TP

+.B \-\-number
+Print an optional packet number at the beginning of the line.
+.TP

 .B \-O
 .B \-O

+.PD 0
+.TP
+.B \-\-no\-optimize
+.PD

 Do not run the packet-matching code optimizer.
 This is useful only
 if you suspect a bug in the optimizer.
 .TP
 .B \-p
 Do not run the packet-matching code optimizer.
 This is useful only
 if you suspect a bug in the optimizer.
 .TP
 .B \-p

+.PD 0
+.TP
+.B \-\-no\-promiscuous\-mode
+.PD

 \fIDon't\fP put the interface
 into promiscuous mode.
 Note that the interface might be in promiscuous
 mode for some other reason; hence, `-p' cannot be used as an abbreviation for
 `ether host {local-hw-addr} or ether broadcast'.
 .TP
 \fIDon't\fP put the interface
 into promiscuous mode.
 Note that the interface might be in promiscuous
 mode for some other reason; hence, `-p' cannot be used as an abbreviation for
 `ether host {local-hw-addr} or ether broadcast'.
 .TP

+.BI \-Q " direction"
+.PD 0
+.TP
+.BI \-\-direction= direction
+.PD
+Choose send/receive direction \fIdirection\fR for which packets should be
+captured. Possible values are `in', `out' and `inout'. Not available
+on all platforms.
+.TP

 .B \-q
 Quick (quiet?) output.
 Print less protocol information so output
 .B \-q
 Quick (quiet?) output.
 Print less protocol information so output


@@ -421,16 +563,24 @@ If specified, \fItcpdump\fP will not print replay prevention field.
 Since there is no protocol version field in ESP/AH specification,
 \fItcpdump\fP cannot deduce the version of ESP/AH protocol.
 .TP
 Since there is no protocol version field in ESP/AH specification,
 \fItcpdump\fP cannot deduce the version of ESP/AH protocol.
 .TP

-.B \-r
+.BI \-r " file"

 Read packets from \fIfile\fR (which was created with the
 .B \-w
 Read packets from \fIfile\fR (which was created with the
 .B \-w

-option).
+option or by other tools that write pcap or pcap-ng files).

 Standard input is used if \fIfile\fR is ``-''.
 .TP
 .B \-S
 Standard input is used if \fIfile\fR is ``-''.
 .TP
 .B \-S

+.PD 0
+.TP
+.B \-\-absolute\-tcp\-sequence\-numbers
+.PD

 Print absolute, rather than relative, TCP sequence numbers.
 .TP
 Print absolute, rather than relative, TCP sequence numbers.
 .TP

-.B \-s
+.BI \-s " snaplen"
+.PD 0
+.TP
+.BI \-\-snapshot\-length= snaplen
+.PD

 Snarf \fIsnaplen\fP bytes of data from each packet rather than the
 default of 65535 bytes.
 Packets truncated because of a limited snapshot
 Snarf \fIsnaplen\fP bytes of data from each packet rather than the
 default of 65535 bytes.
 Packets truncated because of a limited snapshot


@@ -448,20 +598,37 @@ Setting
 for backwards compatibility with recent older versions of
 .IR tcpdump .
 .TP
 for backwards compatibility with recent older versions of
 .IR tcpdump .
 .TP

-.B \-T
+.BI \-T " type"

 Force packets selected by "\fIexpression\fP" to be interpreted the
 specified \fItype\fR.
 Currently known types are
 \fBaodv\fR (Ad-hoc On-demand Distance Vector protocol),
 Force packets selected by "\fIexpression\fP" to be interpreted the
 specified \fItype\fR.
 Currently known types are
 \fBaodv\fR (Ad-hoc On-demand Distance Vector protocol),

+\fBcarp\fR (Common Address Redundancy Protocol),

 \fBcnfp\fR (Cisco NetFlow protocol),
 \fBcnfp\fR (Cisco NetFlow protocol),

+\fBlmp\fR (Link Management Protocol),
+\fBpgm\fR (Pragmatic General Multicast),
+\fBpgm_zmtp1\fR (ZMTP/1.0 inside PGM/EPGM),
+\fBradius\fR (RADIUS),

 \fBrpc\fR (Remote Procedure Call),
 \fBrtp\fR (Real-Time Applications protocol),
 \fBrtcp\fR (Real-Time Applications control protocol),
 \fBsnmp\fR (Simple Network Management Protocol),
 \fBtftp\fR (Trivial File Transfer Protocol),
 \fBvat\fR (Visual Audio Tool),
 \fBrpc\fR (Remote Procedure Call),
 \fBrtp\fR (Real-Time Applications protocol),
 \fBrtcp\fR (Real-Time Applications control protocol),
 \fBsnmp\fR (Simple Network Management Protocol),
 \fBtftp\fR (Trivial File Transfer Protocol),
 \fBvat\fR (Visual Audio Tool),

+\fBwb\fR (distributed White Board),
+\fBzmtp1\fR (ZeroMQ Message Transport Protocol 1.0)

 and
 and

-\fBwb\fR (distributed White Board).
+\fBvxlan\fR (Virtual eXtensible Local Area Network).
+.IP
+Note that the \fBpgm\fR type above affects UDP interpretation only, the native
+PGM is always recognised as IP protocol 113 regardless. UDP-encapsulated PGM is
+often called "EPGM" or "PGM/UDP".
+.IP
+Note that the \fBpgm_zmtp1\fR type above affects interpretation of both native
+PGM and UDP at once. During the native PGM decoding the application data of an
+ODATA/RDATA packet would be decoded as a ZeroMQ datagram with ZMTP/1.0 frames.
+During the UDP decoding in addition to that any UDP packet would be treated as
+an encapsulated PGM packet.

 .TP
 .B \-t
 \fIDon't\fP print a timestamp on each dump line.
 .TP
 .B \-t
 \fIDon't\fP print a timestamp on each dump line.


@@ -484,11 +651,24 @@ on each dump line.
 Print undecoded NFS handles.
 .TP
 .B \-U
 Print undecoded NFS handles.
 .TP
 .B \-U

-Make output saved via the
+.PD 0
+.TP
+.B \-\-packet\-buffered
+.PD
+If the
+.B \-w
+option is not specified, make the printed packet output
+``packet-buffered''; i.e., as the description of the contents of each
+packet is printed, it will be written to the standard output, rather
+than, when not writing to a terminal, being written only when the output
+buffer fills.
+.IP
+If the

 .B \-w
 .B \-w

-option ``packet-buffered''; i.e., as each packet is saved, it will be
-written to the output file, rather than being written only when the
-output buffer fills.
+option is specified, make the saved raw packet output
+``packet-buffered''; i.e., as each packet is saved, it will be written
+to the output file, rather than being written only when the output
+buffer fills.

 .IP
 The
 .B \-U
 .IP
 The
 .B \-U


@@ -525,26 +705,46 @@ With
 .B \-X
 Telnet options are printed in hex as well.
 .TP
 .B \-X
 Telnet options are printed in hex as well.
 .TP

-.B \-w
+.BI \-V " file"
+Read a list of filenames from \fIfile\fR. Standard input is used
+if \fIfile\fR is ``-''.
+.TP
+.BI \-w " file"

 Write the raw packets to \fIfile\fR rather than parsing and printing
 them out.
 They can later be printed with the \-r option.
 Standard output is used if \fIfile\fR is ``-''.
 Write the raw packets to \fIfile\fR rather than parsing and printing
 them out.
 They can later be printed with the \-r option.
 Standard output is used if \fIfile\fR is ``-''.

+.IP
+This output will be buffered if written to a file or pipe, so a program
+reading from the file or pipe may not see packets for an arbitrary
+amount of time after they are received.  Use the
+.B \-U
+flag to cause packets to be written as soon as they are received.
+.IP
+The MIME type \fIapplication/vnd.tcpdump.pcap\fP has been registered
+with IANA for \fIpcap\fP files. The filename extension \fI.pcap\fP
+appears to be the most commonly used along with \fI.cap\fP and
+\fI.dmp\fP. \fITcpdump\fP itself doesn't check the extension when
+reading capture files and doesn't add an extension when writing them
+(it uses magic numbers in the file header instead). However, many
+operating systems and applications will use the extension if it is
+present and adding one (e.g. .pcap) is recommended.
+.IP

 See
 .BR pcap-savefile (@MAN_FILE_FORMATS@)
 for a description of the file format.
 .TP
 .B \-W
 See
 .BR pcap-savefile (@MAN_FILE_FORMATS@)
 for a description of the file format.
 .TP
 .B \-W

-Used in conjunction with the 
-.B \-C 
+Used in conjunction with the
+.B \-C

 option, this will limit the number
 of files created to the specified number, and begin overwriting files
 option, this will limit the number
 of files created to the specified number, and begin overwriting files

-from the beginning, thus creating a 'rotating' buffer. 
+from the beginning, thus creating a 'rotating' buffer.

 In addition, it will name
 the files with enough leading 0s to support the maximum number of
 files, allowing them to sort correctly.
 .IP
 In addition, it will name
 the files with enough leading 0s to support the maximum number of
 files, allowing them to sort correctly.
 .IP

-Used in conjunction with the 
+Used in conjunction with the

 .B \-G
 option, this will limit the number of rotated dump files that get
 created, exiting with status 0 when reaching the limit. If used with
 .B \-G
 option, this will limit the number of rotated dump files that get
 created, exiting with status 0 when reaching the limit. If used with


@@ -554,7 +754,7 @@ as well, the behavior will result in cyclical files per timeslice.
 .B \-x
 When parsing and printing,
 in addition to printing the headers of each packet, print the data of
 .B \-x
 When parsing and printing,
 in addition to printing the headers of each packet, print the data of

-each packet (minus its link level header) in hex. 
+each packet (minus its link level header) in hex.

 The smaller of the entire packet or
 .I snaplen
 bytes will be printed.  Note that this is the entire link-layer
 The smaller of the entire packet or
 .I snaplen
 bytes will be printed.  Note that this is the entire link-layer


@@ -582,10 +782,14 @@ each packet,
 .I including
 its link level header, in hex and ASCII.
 .TP
 .I including
 its link level header, in hex and ASCII.
 .TP

-.B \-y
+.BI \-y " datalinktype"
+.PD 0
+.TP
+.BI \-\-linktype= datalinktype
+.PD

 Set the data link type to use while capturing packets to \fIdatalinktype\fP.
 .TP
 Set the data link type to use while capturing packets to \fIdatalinktype\fP.
 .TP

-.B \-z
+.BI \-z " postrotate-command"

 Used in conjunction with the
 .B -C
 or
 Used in conjunction with the
 .B -C
 or


@@ -593,7 +797,7 @@ or
 options, this will make
 .I tcpdump
 run "
 options, this will make
 .I tcpdump
 run "

-.I command file
+.I postrotate-command file

 " where
 .I file
 is the savefile being closed after each rotation. For example, specifying
 " where
 .I file
 is the savefile being closed after each rotation. For example, specifying


@@ -610,8 +814,15 @@ different arguments, you can always write a shell script that will take the
 savefile name as the only argument, make the flags & arguments arrangements
 and execute the command that you want.
 .TP
 savefile name as the only argument, make the flags & arguments arrangements
 and execute the command that you want.
 .TP

-.B \-Z
-Drops privileges (if root) and changes user ID to
+.BI \-Z " user"
+.PD 0
+.TP
+.BI \-\-relinquish\-privileges= user
+.PD
+If
+.I tcpdump
+is running as root, after opening the capture device or input savefile,
+but before opening any savefiles for output, change the user ID to

 .I user
 and the group ID to the primary group of
 .IR user .
 .I user
 and the group ID to the primary group of
 .IR user .


@@ -628,10 +839,12 @@ only packets for which \fIexpression\fP is `true' will be dumped.
 For the \fIexpression\fP syntax, see
 .BR pcap-filter (@MAN_MISC_INFO@).
 .LP
 For the \fIexpression\fP syntax, see
 .BR pcap-filter (@MAN_MISC_INFO@).
 .LP

-Expression arguments can be passed to \fItcpdump\fP as either a single
-argument or as multiple arguments, whichever is more convenient.
-Generally, if the expression contains Shell metacharacters, it is
-easier to pass it as a single, quoted argument.
+The \fIexpression\fP argument can be passed to \fItcpdump\fP as either a single
+Shell argument, or as multiple Shell arguments, whichever is more convenient.
+Generally, if the expression contains Shell metacharacters, such as
+backslashes used to escape protocol names, it is easier to pass it as
+a single, quoted argument rather than to escape the Shell
+metacharacters.

 Multiple arguments are concatenated with spaces before being parsed.
 .SH EXAMPLES
 .LP
 Multiple arguments are concatenated with spaces before being parsed.
 .SH EXAMPLES
 .LP


@@ -867,8 +1080,8 @@ The general format of a tcp protocol line is:
 \fISrc\fP and \fIdst\fP are the source and destination IP
 addresses and ports.
 \fIFlags\fP are some combination of S (SYN),
 \fISrc\fP and \fIdst\fP are the source and destination IP
 addresses and ports.
 \fIFlags\fP are some combination of S (SYN),

-F (FIN), P (PUSH), R (RST), W (ECN CWR) or E (ECN-Echo), or a single
-`.' (no flags).
+F (FIN), P (PUSH), R (RST), U (URG), W (ECN CWR), E (ECN-Echo) or
+`.' (ACK), or `none' if no flags are set.

 \fIData-seqno\fP describes the portion of sequence space covered
 by the data in this packet (see example below).
 \fIAck\fP is sequence number of the next data expected the other
 \fIData-seqno\fP describes the portion of sequence space covered
 by the data in this packet (see example below).
 \fIAck\fP is sequence number of the next data expected the other


@@ -915,8 +1128,7 @@ bytes and there was a max-segment-size option requesting an mss of
 Csam replies with a similar packet except it includes a piggy-backed
 ack for rtsg's SYN.
 Rtsg then acks csam's SYN.
 Csam replies with a similar packet except it includes a piggy-backed
 ack for rtsg's SYN.
 Rtsg then acks csam's SYN.

-The `.' means no
-flags were set.
+The `.' means the ACK flag was set.

 The packet contained no data so there is no data sequence number.
 Note that the ack sequence
 number is a small integer (1).
 The packet contained no data so there is no data sequence number.
 Note that the ack sequence
 number is a small integer (1).


@@ -1151,7 +1363,7 @@ tcp-push, tcp-act, tcp-urg.
 .PP
 This can be demonstrated as:
 .RS
 .PP
 This can be demonstrated as:
 .RS

-.B 
+.B

      tcpdump -i xl0 'tcp[tcpflags] & tcp-push != 0'
 .RE
 .PP
      tcpdump -i xl0 'tcp[tcpflags] & tcp-push != 0'
 .RE
 .PP


@@ -1262,7 +1474,6 @@ RA, \fInot\fP set) and `|' (truncated message, TC, set).
 If the
 `question' section doesn't contain exactly one entry, `[\fIn\fPq]'
 is printed.
 If the
 `question' section doesn't contain exactly one entry, `[\fIn\fPq]'
 is printed.

-

 .HD
 SMB/CIFS decoding
 .LP
 .HD
 SMB/CIFS decoding
 .LP


@@ -1270,19 +1481,18 @@ SMB/CIFS decoding
 on UDP/137, UDP/138 and TCP/139.
 Some primitive decoding of IPX and
 NetBEUI SMB data is also done.
 on UDP/137, UDP/138 and TCP/139.
 Some primitive decoding of IPX and
 NetBEUI SMB data is also done.

-
+.LP

 By default a fairly minimal decode is done, with a much more detailed
 decode done if -v is used.
 Be warned that with -v a single SMB packet
 may take up a page or more, so only use -v if you really want all the
 gory details.
 By default a fairly minimal decode is done, with a much more detailed
 decode done if -v is used.
 Be warned that with -v a single SMB packet
 may take up a page or more, so only use -v if you really want all the
 gory details.

-
-For information on SMB packet formats and what all te fields mean see
+.LP
+For information on SMB packet formats and what all the fields mean see

 www.cifs.org or the pub/samba/specs/ directory on your favorite
 samba.org mirror site.
 The SMB patches were written by Andrew Tridgell
 ([email protected]).
 www.cifs.org or the pub/samba/specs/ directory on your favorite
 samba.org mirror site.
 The SMB patches were written by Andrew Tridgell
 ([email protected]).

-

 .HD
 NFS Requests and Replies
 .LP
 .HD
 NFS Requests and Replies
 .LP


@@ -1290,39 +1500,45 @@ Sun NFS (Network File System) requests and replies are printed as:
 .RS
 .nf
 .sp .5
 .RS
 .nf
 .sp .5

-\fIsrc.xid > dst.nfs: len op args\fP
-\fIsrc.nfs > dst.xid: reply stat len op results\fP
+\fIsrc.sport > dst.nfs: NFS request xid xid len op args\fP
+\fIsrc.nfs > dst.dport: NFS reply xid xid reply stat len op results\fP

 .sp .5
 \f(CW
 .sp .5
 \f(CW

-sushi.6709 > wrl.nfs: 112 readlink fh 21,24/10.73165
-wrl.nfs > sushi.6709: reply ok 40 readlink "../var"
-sushi.201b > wrl.nfs:
+sushi.1023 > wrl.nfs: NFS request xid 26377
+       112 readlink fh 21,24/10.73165
+wrl.nfs > sushi.1023: NFS reply xid 26377
+       reply ok 40 readlink "../var"
+sushi.1022 > wrl.nfs: NFS request xid 8219

        144 lookup fh 9,74/4096.6878 "xcolors"
        144 lookup fh 9,74/4096.6878 "xcolors"

-wrl.nfs > sushi.201b:
+wrl.nfs > sushi.1022: NFS reply xid 8219

        reply ok 128 lookup fh 9,74/4134.3150
 \fR
 .sp .5
 .fi
 .RE
        reply ok 128 lookup fh 9,74/4134.3150
 \fR
 .sp .5
 .fi
 .RE

-In the first line, host \fIsushi\fP sends a transaction with id \fI6709\fP
-to \fIwrl\fP (note that the number following the src host is a
-transaction id, \fInot\fP the source port).
+In the first line, host \fIsushi\fP sends a transaction with id \fI26377\fP
+to \fIwrl\fP.

 The request was 112 bytes,
 excluding the UDP and IP headers.
 The operation was a \fIreadlink\fP
 (read symbolic link) on file handle (\fIfh\fP) 21,24/10.731657119.
 (If one is lucky, as in this case, the file handle can be interpreted
 as a major,minor device number pair, followed by the inode number and
 The request was 112 bytes,
 excluding the UDP and IP headers.
 The operation was a \fIreadlink\fP
 (read symbolic link) on file handle (\fIfh\fP) 21,24/10.731657119.
 (If one is lucky, as in this case, the file handle can be interpreted
 as a major,minor device number pair, followed by the inode number and

-generation number.)
-\fIWrl\fP replies `ok' with the contents of the link.
+generation number.) In the second line, \fIwrl\fP replies `ok' with
+the same transaction id and the contents of the link.
+.LP
+In the third line, \fIsushi\fP asks (using a new transaction id) \fIwrl\fP
+to lookup the name `\fIxcolors\fP' in directory file 9,74/4096.6878. In
+the fourth line, \fIwrl\fP sends a reply with the respective transaction id.

 .LP
 .LP

-In the third line, \fIsushi\fP asks \fIwrl\fP to lookup the name
-`\fIxcolors\fP' in directory file 9,74/4096.6878.

 Note that the data printed
 depends on the operation type.
 The format is intended to be self
 explanatory if read in conjunction with
 an NFS protocol spec.
 Note that the data printed
 depends on the operation type.
 The format is intended to be self
 explanatory if read in conjunction with
 an NFS protocol spec.

+Also note that older versions of tcpdump printed NFS packets in a
+slightly different format: the transaction id (xid) would be printed
+instead of the non-NFS port number of the packet.

 .LP
 If the \-v (verbose) flag is given, additional information is printed.
 For example:
 .LP
 If the \-v (verbose) flag is given, additional information is printed.
 For example:


@@ -1330,9 +1546,9 @@ For example:
 .nf
 .sp .5
 \f(CW
 .nf
 .sp .5
 \f(CW

-sushi.1372a > wrl.nfs:
+sushi.1023 > wrl.nfs: NFS request xid 79658

        148 read fh 21,11/12.195 8192 bytes @ 24576
        148 read fh 21,11/12.195 8192 bytes @ 24576

-wrl.nfs > sushi.1372a:
+wrl.nfs > sushi.1023: NFS reply xid 79658

        reply ok 1472 read REG 100664 ids 417/0 sz 29388
 \fP
 .sp .5
        reply ok 1472 read REG 100664 ids 417/0 sz 29388
 \fP
 .sp .5


@@ -1408,11 +1624,11 @@ not be useful to people who are not familiar with the workings of
 AFS and RX.
 .LP
 If the -v (verbose) flag is given twice, acknowledgement packets and
 AFS and RX.
 .LP
 If the -v (verbose) flag is given twice, acknowledgement packets and

-additional header information is printed, such as the the RX call ID,
+additional header information is printed, such as the RX call ID,

 call number, sequence number, serial number, and the RX packet flags.
 .LP
 If the -v flag is given twice, additional information is printed,
 call number, sequence number, serial number, and the RX packet flags.
 .LP
 If the -v flag is given twice, additional information is printed,

-such as the the RX call ID, serial number, and the RX packet flags.
+such as the RX call ID, serial number, and the RX packet flags.

 The MTU negotiation information is also printed from RX ack packets.
 .LP
 If the -v flag is given three times, the security index and service id
 The MTU negotiation information is also printed from RX ack packets.
 .LP
 If the -v flag is given three times, the security index and service id


@@ -1635,7 +1851,12 @@ Ethernet interface removed the packet from the wire and when the kernel
 serviced the `new packet' interrupt.
 .SH "SEE ALSO"
 stty(1), pcap(3PCAP), bpf(4), nit(4P), pcap-savefile(@MAN_FILE_FORMATS@),
 serviced the `new packet' interrupt.
 .SH "SEE ALSO"
 stty(1), pcap(3PCAP), bpf(4), nit(4P), pcap-savefile(@MAN_FILE_FORMATS@),

-pcap-filter(@MAN_MISC_INFO@)
+pcap-filter(@MAN_MISC_INFO@), pcap-tstamp(@MAN_MISC_INFO@)
+.LP
+.RS
+.I http://www.iana.org/assignments/media-types/application/vnd.tcpdump.pcap
+.RE
+.LP

 .SH AUTHORS
 The original authors are:
 .LP
 .SH AUTHORS
 The original authors are:
 .LP


@@ -1655,7 +1876,7 @@ The current version is available via http:
 The original distribution is available via anonymous ftp:
 .LP
 .RS
 The original distribution is available via anonymous ftp:
 .LP
 .RS

-.I ftp://ftp.ee.lbl.gov/tcpdump.tar.Z
+.I ftp://ftp.ee.lbl.gov/old/tcpdump.tar.Z

 .RE
 .LP
 IPv6/IPsec support is added by WIDE/KAME project.
 .RE
 .LP
 IPv6/IPsec support is added by WIDE/KAME project.