dect
/
libpcap
Archived
13
0
Fork 0
Code Releases Activity

Use a semicolon, rather than a comma, to separate the DLT_ and LINKTYPE_ 

types in the item headers, so as to make it less likely that people will
assume that the numerical values given for LINKTYPE_ types are also the
numerical values for the DLT_ types (in some cases, they aren't).
This commit is contained in:
guy 2008-10-27 22:52:30 +00:00
parent e58ca4c1ad
commit e8cb2f6a99
1 changed files with 26 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
pcap-linktype.manmisc.in
View File

@ -1,4 +1,4 @@
.\" @(#) $Header: /tcpdump/master/libpcap/pcap-linktype.manmisc.in,v 1.2 2008-10-24 07:33:50 guy Exp $ .\" @(#) $Header: /tcpdump/master/libpcap/pcap-linktype.manmisc.in,v 1.3 2008-10-27 22:52:30 guy Exp $
.\" .\"
.\" Copyright (c) 1987, 1988, 1989, 1990, 1991, 1992, 1994, 1995, 1996, 1997 .\" Copyright (c) 1987, 1988, 1989, 1990, 1991, 1992, 1994, 1995, 1996, 1997
.\" The Regents of the University of California. All rights reserved. .\" The Regents of the University of California. All rights reserved.
@ -55,7 +55,7 @@ applications should check for particular
values by name. values by name.
.RS 5 .RS 5
.TP 5 .TP 5
.BR DLT_NULL ", " LINKTYPE_NULL = 0 .BR DLT_NULL "; " LINKTYPE_NULL = 0
BSD loopback encapsulation; the link layer header is a 4-byte field, in BSD loopback encapsulation; the link layer header is a 4-byte field, in
.I host .I host
byte order, containing a PF_ value from byte order, containing a PF_ value from
@ -72,24 +72,24 @@ values are
.I not .I not
necessarily those of the machine reading the capture file. necessarily those of the machine reading the capture file.
.TP 5 .TP 5
.BR DLT_EN10MB ", " LINKTYPE_ETHERNET = 1 .BR DLT_EN10MB "; " LINKTYPE_ETHERNET = 1
Ethernet (10Mb, 100Mb, 1000Mb, and up); the Ethernet (10Mb, 100Mb, 1000Mb, and up); the
.B 10MB .B 10MB
in the in the
.B DLT_ .B DLT_
name is historical. name is historical.
.TP 5 .TP 5
.BR DLT_IEEE802 ", " LINKTYPE_TOKEN_RING = 6 .BR DLT_IEEE802 "; " LINKTYPE_TOKEN_RING = 6
IEEE 802.5 Token Ring; the IEEE 802.5 Token Ring; the
.B IEEE802 .B IEEE802
in the in the
.B DLT_ .B DLT_
name is historical. name is historical.
.TP 5 .TP 5
.BR DLT_ARCNET ", " LINKTYPE_ARCNET = 7 .BR DLT_ARCNET "; " LINKTYPE_ARCNET = 7
ARCNET ARCNET
.TP 5 .TP 5
.BR DLT_SLIP ", " LINKTYPE_SLIP = 8 .BR DLT_SLIP "; " LINKTYPE_SLIP = 8
SLIP; the link layer header contains, in order: SLIP; the link layer header contains, in order:
.RS 10 .RS 10
.LP .LP
@ -121,40 +121,40 @@ COMPRESSED_TCP, the compressed TCP/IP datagram header;
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 .RE
.TP 5 .TP 5
.BR DLT_PPP ", " LINKTYPE_PPP = 9 .BR DLT_PPP "; " LINKTYPE_PPP = 9
PPP; if the first 2 bytes are 0xff and 0x03, it's PPP in HDLC-like 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 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 .TP 5
.BR DLT_FDDI ", " LINKTYPE_FDDI = 10 .BR DLT_FDDI "; " LINKTYPE_FDDI = 10
FDDI FDDI
.TP 5 .TP 5
.BR DLT_ATM_RFC1483 ", " LINKTYPE_ATM_RFC1483 = 100 .BR DLT_ATM_RFC1483 "; " LINKTYPE_ATM_RFC1483 = 100
RFC 1483 LLC/SNAP-encapsulated ATM; the packet begins with an IEEE 802.2 RFC 1483 LLC/SNAP-encapsulated ATM; the packet begins with an IEEE 802.2
LLC header. LLC header.
.TP 5 .TP 5
.BR DLT_RAW ", " LINKTYPE_RAW = 101 .BR DLT_RAW "; " LINKTYPE_RAW = 101
raw IP; the packet begins with an IP header. raw IP; the packet begins with an IP header.
.TP 5 .TP 5
.BR DLT_PPP_SERIAL ", " LINKTYPE_PPP_HDLC = 50 .BR DLT_PPP_SERIAL "; " LINKTYPE_PPP_HDLC = 50
PPP in HDLC-like framing, as per RFC 1662, or Cisco PPP with HDLC 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 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 for PPP in HDLC-like framing, and will be 0x0F or 0x8F for Cisco PPP
with HDLC framing. with HDLC framing.
.TP 5 .TP 5
.BR DLT_PPP_ETHER ", " LINKTYPE_PPP_ETHER = 51 .BR DLT_PPP_ETHER "; " LINKTYPE_PPP_ETHER = 51
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 .TP 5
.BR DLT_C_HDLC ", " LINKTYPE_C_HDLC = 104 .BR DLT_C_HDLC "; " LINKTYPE_C_HDLC = 104
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 .TP 5
.BR DLT_IEEE802_11 ", " LINKTYPE_IEEE802_11 = 105 .BR DLT_IEEE802_11 "; " LINKTYPE_IEEE802_11 = 105
IEEE 802.11 wireless LAN IEEE 802.11 wireless LAN
.TP 5 .TP 5
.BR DLT_FRELAY ", " LINKTYPE_FRELAY = 107 .BR DLT_FRELAY "; " LINKTYPE_FRELAY = 107
Frame Relay Frame Relay
.TP 5 .TP 5
.BR DLT_LOOP ", " LINKTYPE_LOOP = 108 .BR DLT_LOOP "; " LINKTYPE_LOOP = 108
OpenBSD loopback encapsulation; the link layer header is a 4-byte field, in OpenBSD loopback encapsulation; the link layer header is a 4-byte field, in
.I network .I network
byte order, containing a PF_ value from OpenBSD's byte order, containing a PF_ value from OpenBSD's
@ -165,7 +165,7 @@ Note that, if a ``savefile'' is being read, those PF_ values are
.I not .I not
necessarily those of the machine reading the capture file. necessarily those of the machine reading the capture file.
.TP 5 .TP 5
.BR DLT_LINUX_SLL ", " LINKTYPE_LINUX_SLL = 113 .BR DLT_LINUX_SLL "; " LINKTYPE_LINUX_SLL = 113
Linux "cooked" capture encapsulation; the link layer header contains, in Linux "cooked" capture encapsulation; the link layer header contains, in
order: order:
.RS 10 .RS 10
@ -203,10 +203,10 @@ order, or containing 1 for Novell 802.3 frames without an 802.2 LLC
header or 4 for frames beginning with an 802.2 LLC header. header or 4 for frames beginning with an 802.2 LLC header.
.RE .RE
.TP 5 .TP 5
.BR DLT_LTALK ", " LINKTYPE_LTALK = 104 .BR DLT_LTALK "; " LINKTYPE_LTALK = 104
Apple LocalTalk; the packet begins with an AppleTalk LLAP header. Apple LocalTalk; the packet begins with an AppleTalk LLAP header.
.TP 5 .TP 5
.BR DLT_PFLOG ", " LINKTYPE_PFLOG = 117 .BR DLT_PFLOG "; " LINKTYPE_PFLOG = 117
OpenBSD pflog; the link layer header contains a OpenBSD pflog; the link layer header contains a
.B "struct pfloghdr" .B "struct pfloghdr"
structure, as defined by the host on which the file was saved. (This structure, as defined by the host on which the file was saved. (This
@ -214,14 +214,14 @@ differs from operating system to operating system and release to
release; there is nothing in the file to indicate what the layout of release; there is nothing in the file to indicate what the layout of
that structure is.) that structure is.)
.TP 5 .TP 5
.BR DLT_PRISM_HEADER ", " LINKTYPE_PRISM_HEADER = 119 .BR DLT_PRISM_HEADER "; " LINKTYPE_PRISM_HEADER = 119
Prism monitor mode information followed by an 802.11 header. Prism monitor mode information followed by an 802.11 header.
.TP 5 .TP 5
.BR DLT_IP_OVER_FC ", " LINKTYPE_IP_OVER_FC = 122 .BR DLT_IP_OVER_FC "; " LINKTYPE_IP_OVER_FC = 122
RFC 2625 IP-over-Fibre Channel, with the link-layer header being the RFC 2625 IP-over-Fibre Channel, with the link-layer header being the
Network_Header as described in that RFC. Network_Header as described in that RFC.
.TP 5 .TP 5
.BR DLT_SUNATM ", " LINKTYPE_SUNATM = 123 .BR DLT_SUNATM "; " LINKTYPE_SUNATM = 123
SunATM devices; the link layer header contains, in order: SunATM devices; the link layer header contains, in order:
.RS 10 .RS 10
.LP .LP
@ -258,22 +258,22 @@ a 1-byte VPI value;
a 2-byte VCI field, in network byte order. a 2-byte VCI field, in network byte order.
.RE .RE
.TP 5 .TP 5
.BR DLT_IEEE802_11_RADIO ", " LINKTYPE_IEEE802_11_RADIO = 127 .BR DLT_IEEE802_11_RADIO "; " LINKTYPE_IEEE802_11_RADIO = 127
link-layer information followed by an 802.11 header - see link-layer information followed by an 802.11 header - see
http://www.shaftnet.org/~pizza/software/capturefrm.txt for a description http://www.shaftnet.org/~pizza/software/capturefrm.txt for a description
of the link-layer information. of the link-layer information.
.TP 5 .TP 5
.BR DLT_ARCNET_LINUX ", " LINKTYPE_ARCNET_LINUX = 129 .BR DLT_ARCNET_LINUX "; " LINKTYPE_ARCNET_LINUX = 129
ARCNET, with no exception frames, reassembled packets rather than raw ARCNET, with no exception frames, reassembled packets rather than raw
frames, and an extra 16-bit offset field between the destination host frames, and an extra 16-bit offset field between the destination host
and type bytes. and type bytes.
.TP 5 .TP 5
.BR DLT_LINUX_IRDA ", " LINKTYPE_LINUX_IRDA = 144 .BR DLT_LINUX_IRDA "; " LINKTYPE_LINUX_IRDA = 144
Linux-IrDA packets, with a Linux-IrDA packets, with a
.B DLT_LINUX_SLL .B DLT_LINUX_SLL
header followed by the IrLAP header. header followed by the IrLAP header.
.TP 5 .TP 5
.BR DLT_LINUX_LAPD ", " LINKTYPE_LINUX_LAPD = 177 .BR DLT_LINUX_LAPD "; " LINKTYPE_LINUX_LAPD = 177
LAPD (Q.921) frames, with a LAPD (Q.921) frames, with a
.B DLT_LINUX_SLL .B DLT_LINUX_SLL
header captured via vISDN. header captured via vISDN.