Update the date.
Add some periods to the ends of long DLT_ descriptions. Add some missing DLT_ values.
This commit is contained in:
parent
a08248f680
commit
ecaf2b3929
106
pcap.3
106
pcap.3
|
@ -1,4 +1,4 @@
|
|||
.\" @(#) $Header: /tcpdump/master/libpcap/Attic/pcap.3,v 1.52 2003-11-16 10:07:35 guy Exp $
|
||||
.\" @(#) $Header: /tcpdump/master/libpcap/Attic/pcap.3,v 1.53 2003-11-18 21:51:11 guy Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1994, 1996, 1997
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
|
@ -19,7 +19,7 @@
|
|||
.\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
|
||||
.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
|
||||
.\"
|
||||
.TH PCAP 3 "3 January 2001"
|
||||
.TH PCAP 3 "18 November 2003"
|
||||
.SH NAME
|
||||
pcap \- Packet Capture library
|
||||
.SH SYNOPSIS
|
||||
|
@ -701,7 +701,7 @@ BSD loopback encapsulation; the link layer header is a 4-byte field, in
|
|||
.I host
|
||||
byte order, containing a PF_ value from
|
||||
.B socket.h
|
||||
for the network-layer protocol of the packet
|
||||
for the network-layer protocol of the packet.
|
||||
.IP
|
||||
Note that ``host byte order'' is the byte order of the machine on which
|
||||
the packets are captured, and the PF_ values are for the OS of the
|
||||
|
@ -751,35 +751,35 @@ COMPRESSED_TCP, the compressed TCP/IP datagram header;
|
|||
.RE
|
||||
.RS 5
|
||||
.LP
|
||||
for a total of 16 bytes; the uncompressed IP datagram follows the header
|
||||
for a total of 16 bytes; the uncompressed IP datagram follows the header.
|
||||
.RE
|
||||
.TP 5
|
||||
.B DLT_PPP
|
||||
PPP; if the first 2 bytes are 0xff and 0x03, it's PPP in HDLC-like
|
||||
framing, with the PPP header following those two bytes, otherwise it's
|
||||
PPP without framing, and the packet begins with the PPP header
|
||||
PPP without framing, and the packet begins with the PPP header.
|
||||
.TP 5
|
||||
.B DLT_FDDI
|
||||
FDDI
|
||||
.TP 5
|
||||
.B DLT_ATM_RFC1483
|
||||
RFC 1483 LLC/SNAP-encapsulated ATM; the packet begins with an IEEE 802.2
|
||||
LLC header
|
||||
LLC header.
|
||||
.TP 5
|
||||
.B DLT_RAW
|
||||
raw IP; the packet begins with an IP header
|
||||
raw IP; the packet begins with an IP header.
|
||||
.TP 5
|
||||
.B DLT_PPP_SERIAL
|
||||
PPP in HDLC-like framing, as per RFC 1662, or Cisco PPP with HDLC
|
||||
framing, as per section 4.3.1 of RFC 1547; the first byte will be 0xFF
|
||||
for PPP in HDLC-like framing, and will be 0x0F or 0x8F for Cisco PPP
|
||||
with HDLC framing
|
||||
with HDLC framing.
|
||||
.TP 5
|
||||
.B DLT_PPP_ETHER
|
||||
PPPoE; the packet begins with a PPPoE header, as per RFC 2516
|
||||
PPPoE; the packet begins with a PPPoE header, as per RFC 2516.
|
||||
.TP 5
|
||||
.B DLT_C_HDLC
|
||||
Cisco PPP with HDLC framing, as per section 4.3.1 of RFC 1547
|
||||
Cisco PPP with HDLC framing, as per section 4.3.1 of RFC 1547.
|
||||
.TP 5
|
||||
.B DLT_IEEE802_11
|
||||
IEEE 802.11 wireless LAN
|
||||
|
@ -792,7 +792,7 @@ OpenBSD loopback encapsulation; the link layer header is a 4-byte field, in
|
|||
.I network
|
||||
byte order, containing a PF_ value from OpenBSD's
|
||||
.B socket.h
|
||||
for the network-layer protocol of the packet
|
||||
for the network-layer protocol of the packet.
|
||||
.IP
|
||||
Note that, if a ``savefile'' is being read, those PF_ values are
|
||||
.I not
|
||||
|
@ -837,7 +837,72 @@ header or 4 for frames beginning with an 802.2 LLC header.
|
|||
.RE
|
||||
.TP 5
|
||||
.B DLT_LTALK
|
||||
Apple LocalTalk; the packet begins with an AppleTalk LLAP header
|
||||
Apple LocalTalk; the packet begins with an AppleTalk LLAP header.
|
||||
.TP 5
|
||||
.B DLT_PFLOG
|
||||
OpenBSD pflog; the link layer header contains, in order:
|
||||
.RS 10
|
||||
.LP
|
||||
a 4-byte PF_ value, in network byte order;
|
||||
.LP
|
||||
a 16-character interface name;
|
||||
.LP
|
||||
a 2-byte rule number, in network byte order;
|
||||
.LP
|
||||
a 2-byte reason code, in network byte order, which is one of:
|
||||
.RS 5
|
||||
.TP 5
|
||||
0
|
||||
match
|
||||
.TP 5
|
||||
1
|
||||
bad offset
|
||||
.TP 5
|
||||
2
|
||||
fragment
|
||||
.TP 5
|
||||
3
|
||||
short
|
||||
.TP 5
|
||||
4
|
||||
normalize
|
||||
.TP 5
|
||||
memory
|
||||
.RE
|
||||
.LP
|
||||
a 2-byte action code, in network byte order, which is one of:
|
||||
.RS 5
|
||||
.TP 5
|
||||
0
|
||||
passed
|
||||
.TP 5
|
||||
1
|
||||
dropped
|
||||
.TP 5
|
||||
2
|
||||
scrubbed
|
||||
.RE
|
||||
.LP
|
||||
a 2-byte direction, in network byte order, which is one of:
|
||||
.RS 5
|
||||
.TP 5
|
||||
0
|
||||
incoming or outgoing
|
||||
.TP 5
|
||||
1
|
||||
incoming
|
||||
.TP 5
|
||||
2
|
||||
outgoing
|
||||
.RE
|
||||
.RE
|
||||
.TP 5
|
||||
.B DLT_PRISM_HEADER
|
||||
Prism monitor mode information followed by an 802.11 header.
|
||||
.TP 5
|
||||
.B DLT_IP_OVER_FC
|
||||
RFC 2625 IP-over-Fibre Channel, with the link-layer header being the
|
||||
Network_Header as described in that RFC.
|
||||
.TP 5
|
||||
.B DLT_SUNATM
|
||||
SunATM devices; the link layer header contains, in order:
|
||||
|
@ -876,9 +941,20 @@ a 1-byte VPI value;
|
|||
a 2-byte VCI field, in network byte order.
|
||||
.RE
|
||||
.TP 5
|
||||
.B DLT_IP_OVER_FC
|
||||
RFC 2625 IP-over-Fibre Channel, with the link-layer header being the
|
||||
Network_Header as described in that RFC.
|
||||
.B DLT_IEEE802_11_RADIO
|
||||
link-layer information followed by an 802.11 header - see
|
||||
http://www.shaftnet.org/~pizza/software/capturefrm.txt for a description
|
||||
of the link-layer information.
|
||||
.TP 5
|
||||
.B DLT_ARCNET_LINUX
|
||||
ARCNET, with no exception frames, reassembled packets rather than raw
|
||||
frames, and an extra 16-bit offset field between the destination host
|
||||
and type bytes.
|
||||
.TP 5
|
||||
.B DLT_LINUX_IRDA
|
||||
Linux-IrDA packets, with a
|
||||
.B DLT_LINUX_SLL
|
||||
header followed by the IrLAP header.
|
||||
.RE
|
||||
.PP
|
||||
.B pcap_list_datalinks()
|
||||
|
|
Reference in New Issue