Note that on Linux 2.0[.x] kernels, capturing on some PPP devices won't

work correctly (because not all PPP devices have the same link-layer
headers, but we don't try to figure out what type of link-layer header
they'll have, and we can't work around that with PF_PACKET/SOCK_DGRAM
cooked-mode capture if the kernel doesn't support PF_PACKET sockets, and
2.0[.x] kernels don't support PF_PACKET sockets).

diff --git a/tcpdump.1 b/tcpdump.1
index cd2d6b66ca6d35f9887a6d5db5cb419f22c0dcf9..74fa4ea7d7cce95a0e07d68531babf15be369143 100644 (file)
--- a/tcpdump.1
+++ b/tcpdump.1
@@ -1,4 +1,4 @@
-.\" @(#) $Header: /tcpdump/master/tcpdump/Attic/tcpdump.1,v 1.116 2002-02-08 06:45:05 guy Exp $ (LBL)
+.\" @(#) $Header: /tcpdump/master/tcpdump/Attic/tcpdump.1,v 1.117 2002-02-10 00:36:40 guy Exp $ (LBL)
 .\"
 .\" Copyright (c) 1987, 1988, 1989, 1990, 1991, 1992, 1994, 1995, 1996, 1997
 .\"    The Regents of the University of California.  All rights reserved.
@@ -1898,7 +1898,9 @@ will be copied from the kernel (the 2.0[.x] packet capture mechanism, if
 asked to copy only part of a packet to userland, will not report the
 true length of the packet; this would cause most IP packets to get an
 error from
-.BR tcpdump ).
+.BR tcpdump );
+.IP
+capturing on some PPP devices won't work correctly.
 .LP
 We recommend that you upgrade to a 2.2 or later kernel.
 .LP