| Internet-Draft | pcaplinktype | November 2024 |
| Harris & Richardson | Expires 26 May 2025 | [Page] |
This document creates an IANA registry for the PCAP and PCAPNG LINKTYPE values. The PCAP and PCAPNG formats are used to save network captures from programs such as tcpdump and wireshark, when using libraries such as libpcap.¶
This note is to be removed before publishing as an RFC.¶
Status information for this document may be found at https://datatracker.ietf.org/doc/draft-ietf-opsawg-pcaplinktype/.¶
Discussion of this document takes place on the opsawg Working Group mailing list (mailto:[email protected]), which is archived at https://mailarchive.ietf.org/arch/browse/opsawg/. Subscribe at https://www.ietf.org/mailman/listinfo/opsawg/.¶
Source for this draft and an issue tracker can be found at https://github.com/IETF-OPSAWG-WG/pcapng.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 26 May 2025.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
In the late 1980's, Van Jacobson, Steve McCanne, and others at the Network Research Group at Lawrence Berkeley National Laboratory developed the tcpdump program to capture and dissect network traces. The code to capture traffic, using low-level mechanisms in various operating systems, and to read and write network traces to a file was later put into a library named libpcap [LIBPCAP].¶
Other documents describe the original (legacy) format used by tcpdump (pcap), as well as the revised format (pcapng) which is used by tcpdump and Wireshark [Wireshark].¶
Within those formats each packet that is captured is described by a LINKTYPE value. The LINKTYPE value selects one of many hundred formats for metadata and Layer 2 encapsulation of the packet.¶
This document creates an IANA registry for the LINKTYPE format, establishing the IANA Considerations by which other uses of the pcap and pcapng formats may register new LINKTYPE values.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
IANA is requested to create a new registry group entitled "The PCAP Registry".¶
IANA is also requested to create a registry entitled "PCAP LinkType List" under The PCAP registry group (Section 3.1).¶
The registry has the following structure:¶
LINKTYPE Name: Indicates the symbolic name for this LinkType. The name is prefixed with "LINKTYPE_" (i.e., LINKTYPE_something).¶
LINKTYPE Value: Indicates the integer value assigned for this LinkType.¶
Description: Provides a very short description.¶
Reference: Indicates an authoritative the document reference for the LinkType or a requester reference.¶
The LinkType value is a 16-bit number. The policy allocation for the LinkType values is as follows:¶
Values from 32768 to 65000 must be allocated via Specification Required (Section 4.6 of [RFC8126]). Guidance for Designated Experts is provided in Section 3.2.2.¶
Values from 0 to 32767 are allocated following a First-Come First-Served policy (Section 4.4 of [RFC8126]). Note that this category includes the historical allocations which have an uneven level of definition.¶
Values from 65001 to 65535 are reserved for Private Use (Section 4.1 of [RFC8126]).¶
The initial version of the registry is provided in Section 3.2.1. In each case here, the reference should be to [TCPDUMP] and the RFC number to be assigned to this document, which is not repeated each time.¶
The initial values table is based upon the Link type list maintained by libpcap, and published on [TCPDUMP].¶
Note that historically, values were assigned incrementally following First Come First Served policy, with a preference for a public specification, but with no mandate. Some historical values may have less specification than desired.¶
LinkType values 147 to 162 named LINKTYPE_RESERVED_xx were originally reserved for Private Use. Their use is Deprecated in favour of the values in the 65001-65535 range.¶
In general, Private Use values should never leak out of the entity that uses it. As the First Come First Served range is large and easily obtained, official values are recommended.¶
There is often an associated DLT value which is often identical in value, but not universally so. DLT values are associated with specific operation system captures, and are operating system specific, and are thus not subject to standardization.¶
This is the initial table for the registry:¶
LINKTYPE_C_HDLC¶
104¶
Cisco PPP with HDLC framing¶
Section 4.3.1 of [RFC1547]¶
LINKTYPE_IEEE802_11_AIRONET¶
120¶
Reserved for 802.11 + FreeFreeBSD Aironet radio metadata¶
LINKTYPE_IP_OVER_FC¶
122¶
IP-over-Fibre Channel, starting with the Network_Header¶
LINKTYPE_IEEE802_11_RADIOTAP¶
127¶
Radiotap header, followed by an 802.11 header¶
LINKTYPE_ARCNET_LINUX¶
129¶
ARCNET Data Packets, per RFC 1051 frames w/variations¶
LINKTYPE_APPLE_IP_OVER_IEEE1394¶
138¶
Apple IP-over-IEEE 1394 cooked header¶
LINKTYPE_MTP2_WITH_PHDR¶
139¶
Signaling System 7 (SS7) Message Transfer Part Level¶
LINKTYPE_SCCP¶
142¶
SS7 Control Part, with no MTP3 or MTP2 header¶
LINKTYPE_IEEE802_11_AVS¶
163¶
AVS header, followed by an 802.11 header¶
LINKTYPE_BACNET_MS_TP¶
165¶
BACnet MS/TP frames¶
Section 9.3 MS/TP Frame Format of [ASHRAE-135]¶
LINKTYPE_PPP_PPPD¶
166¶
PPP in HDLC-like encapsulation, like LINKTYPE_PPP_HDLC, different stuffing¶
LINKTYPE_GPRS_LLC¶
169¶
General Packet Radio Service Logical Link Control, as per 3GPP TS 04.64¶
LINKTYPE_GPF_T¶
170¶
Transparent-mapped generic framing procedure¶
LINKTYPE_GCOM_SERIAL¶
173¶
Reserved for Gcom T1/E1 line monitoring equipment¶
LINKTYPE_MFR¶
182¶
FRF.16.1 Multi-Link Frame Relay frames, beginning with an FRF.12 Interface fragmentation format fragmentation header¶
LINKTYPE_A653_ICM¶
185¶
Reserved for Arinc 653 Interpartition Communication messages¶
LINKTYPE_USB_FREEBSD¶
186¶
USB packets, beginning with a FreeBSD USB header¶
LINKTYPE_BLUETOOTH_HCI_H4¶
187¶
Bluetooth HCI UART transport layer; the frame contains an HCI packet indicator octet, as specified by the UART Transport Layer portion of the most recent Bluetooth Core specification, followed by an HCI packet of the specified packet type, as specified by the Host Controller Interface Functional Specification portion of the most recent Bluetooth Core Specification¶
LINKTYPE_IEEE802_16_MAC_CPS¶
188¶
Reserved for IEEE 802.16 MAC Common Part Sublayer¶
LINKTYPE_USB_LINUX¶
189¶
USB packets, beginning with a Linux USB header, as specified by the struct usbmon_packet in the Documentation/usb/usbmon.txt file in the Linux source tree. Only the first 48 octets of that header are present. All fields in the header are in host byte order. When performing a live capture, the host byte order is the byte order of the machine on which the packets are captured. When reading a pcap file, the byte order is the byte order for the file, as specified by the file's magic number; when reading a pcapng file, the byte order is the byte order for the section of the pcapng file, as specified by the Section Header Block¶
LINKTYPE_CAN20B¶
190¶
Reserved for Controller Area Network (CAN) v. 2.0B packets¶
LINKTYPE_IEEE802_15_4_LINUX¶
191¶
IEEE 802.15.4, with address fields padded, as is done by Linux drivers¶
LINKTYPE_PPI¶
192¶
Per-Packet Information information, as specified by the Per-Packet Information Header Specification , followed by a packet with the LINKTYPE_ value specified by the pph_dlt field of that header¶
LINKTYPE_IEEE802_16_MAC_CPS_RADIO¶
193¶
Reserved for 802.16 MAC Common Part Sublayer plus radio header¶
LINKTYPE_IEEE802_15_4_WITHFCS¶
195¶
IEEE 802.15.4 Low-Rate Wireless Networks, with each packet having the FCS at the end of the frame¶
LINKTYPE_SITA¶
196¶
Various link-layer types, with a pseudo-header¶
LINKTYPE_RAIF1¶
198¶
Reserved for Ethernet packets captured from a u10 Networks board¶
LINKTYPE_IPMB_KONTRON¶
199¶
Reserved for IPMB packet for IPMI, with a 2-octet header¶
LINKTYPE_BLUETOOTH_HCI_H4_WITH_PHDR¶
201¶
Bluetooth HCI UART transport layer; the frame contains a 4-octet direction field, in network byte order (big-endian), the low-order bit of which is set if the frame was sent from the host to the controller and clear if the frame was received by the host from the controller, followed by an HCI packet indicator octet, as specified by the UART Transport Layer portion of the most recent Bluetooth Core specification, followed by an HCI packet of the specified packet type, as specified by the Host Controller Interface Functional Specification portion of the most recent Bluetooth Core Specification¶
LINKTYPE_LAPD¶
203¶
Link Access Procedures on the D Channel (LAPD) frames, starting with the address field, with no pseudo-header¶
LINKTYPE_PPP_WITH_DIR¶
204¶
PPP, as per RFC 1661 and RFC 1662 , preceded with a one-octet pseudo-header with a zero value meaning received by this host and a non-zero value meaning sent by this host; if the first 2 octets are 0xff and 0x03, it's PPP in HDLC-like framing, with the PPP header following those two octets, otherwise it's PPP without framing, and the packet begins with the PPP header. The data in the frame is not octet-stuffed or bit-stuffed¶
LINKTYPE_C_HDLC_WITH_DIR¶
205¶
Cisco PPP with HDLC framing, preceded with a one-octet pseudo-header with a zero value meaning received by this host and a non-zero value meaning sent by this host¶
Section 4.3.1 of [RFC1547]¶
LINKTYPE_FRELAY_WITH_DIR¶
206¶
Frame Relay LAPF frames, beginning with a one-octet pseudo-header with a zero value meaning received by this host (DCE->DTE) and a non-zero value meaning sent by this host (DTE->DCE), followed by an ITU-T Recommendation Q.922 LAPF header starting with the address field, and without an FCS at the end of the frame¶
LINKTYPE_LAPB_WITH_DIR¶
207¶
Link Access Procedure, Balanced (LAPB), as specified by ITU-T Recommendation X.25 , preceded with a one-octet pseudo-header with a zero value meaning received by this host (DCE->DTE) and a non-zero value meaning sent by this host (DTE->DCE)¶
LINKTYPE_FLEXRAY¶
210¶
FlexRay frames or symbols, with a pseudo-header¶
LINKTYPE_MOST¶
211¶
Reserved for Media Oriented Systems Transport (MOST) bus¶
LINKTYPE_LIN¶
212¶
Local Interconnect Network (LIN) automotive bus¶
LINKTYPE_IEEE802_15_4_NONASK_PHY¶
215¶
IEEE 802.15.4 Low-Rate Wireless Networks, with each packet having the FCS at the end of the frame, and with the PHY-level data for the O-QPSK, BPSK, GFSK, MSK, and RCC DSS BPSK PHYs (4 octets of 0 as preamble, one octet of SFD, one octet of frame length + reserved bit) preceding the MAC-layer data (starting with the frame control field)¶
LINKTYPE_GSMTAP_ABIS¶
218¶
Reserved for GSM Abis interface, with gsmtap header¶
LINKTYPE_USB_LINUX_MMAPPED¶
220¶
USB packets, beginning with a Linux USB header, as specified by the struct usbmon_packet in the Documentation/usb/usbmon.txt file in the Linux source tree. All 64 octets of the header are present. All fields in the header are in host byte order. When performing a live capture, the host byte order is the byte order of the machine on which the packets are captured. When reading a pcap file, the byte order is the byte order for the file, as specified by the file's magic number; when reading a pcapng file, the byte order is the byte order for the section of the pcapng file, as specified by the Section Header Block. For isochronous transfers, the ndesc field specifies the number of isochronous descriptors that follow¶
LINKTYPE_WIHART¶
223¶
Reserved for Wireless HART (Highway Addressable Remote Transducer)¶
LINKTYPE_FC_2¶
224¶
Fibre Channel FC-2 frames, beginning with a Frame_Header¶
LINKTYPE_FC_2_WITH_FRAME_DELIMS¶
225¶
Fibre Channel FC-2 frames, beginning an encoding of the SOF, followed by a Frame_Header, and ending with an encoding of the SOF. The encodings represent the frame delimiters as 4-octet sequences representing the corresponding ordered sets, with K28.5 represented as 0xBC, and the D symbols as the corresponding octet values; for example, SOFi2, which is K28.5 - D21.5 - D1.2 - D21.2, is represented as 0xBC 0xB5 0x55 0x55¶
LINKTYPE_IEEE802_15_4_NOFCS¶
230¶
IEEE 802.15.4 Low-Rate Wireless Network, without the FCS at the end of the frame¶
LINKTYPE_DBUS¶
231¶
Raw D-Bus messages , starting with the endianness flag, followed by the message type, etc., but without the authentication handshake before the message sequence¶
LINKTYPE_MUX27010¶
236¶
Variant of 3GPP TS 27.010 multiplexing protocol¶
LINKTYPE_STANAG_5066_D_PDU¶
237¶
D_PDUs as described by NATO standard STANAG 5066, starting with the synchronization sequence, and including both header and data CRCs. The current version of STANAG 5066 is backwards-compatible with the 1.0.2 version , although newer versions are classified¶
LINKTYPE_NFLOG¶
239¶
Linux netlink NETLINK NFLOG socket log messages¶
LINKTYPE_NETANALYZER¶
240¶
Ethernet frames with netANALYZER pseudo-header¶
LINKTYPE_NETANALYZER_TRANSPARENT¶
241¶
Ethernet frames with netANALYZER pseudo-header, preamble, and SFD¶
LINKTYPE_MPEG_2_TS¶
243¶
MPEG-2 Transport Stream transport packets¶
Table 2-2 of section 2.4.3.2 Transport Stream packet layer of [H.222.0]¶
LINKTYPE_NFC_LLCP¶
245¶
NFC Logical Link Control Protocol frames, with a pseudo-header¶
LINKTYPE_INFINIBAND¶
247¶
Raw InfiniBand frames, starting with the Local Routing Header, as specified in Chapter 5 Data packet format of InfiniBand™ Architectural Specification Release 1.2.1 Volume 1 - General Specifications¶
LINKTYPE_SCTP¶
248¶
SCTP packets, as defined by RFC 4960 , with no lower-level protocols such as IPv4 or IPv6¶
LINKTYPE_USBPCAP¶
249¶
USB packets, beginning with a USBPcap header¶
LINKTYPE_RTAC_SERIAL¶
250¶
Serial-line packet from the Schweitzer Engineering Laboratories RTAC product¶
LINKTYPE_BLUETOOTH_LE_LL¶
251¶
Bluetooth Low Energy air interface Link Layer packets, in the format described in Section 2.1 (PACKET FORMAT) of volume 6 of the Bluetooth Specification Version 4.0 (see PDF page 2200), but without the Preamble¶
LINKTYPE_BLUETOOTH_BREDR_BB¶
255¶
Bluetooth Basic Rate and Enhanced Data Rate baseband packets¶
LINKTYPE_BLUETOOTH_LE_LL_WITH_PHDR¶
256¶
Bluetooth Low Energy link-layer packets¶
LINKTYPE_PROFIBUS_DL¶
257¶
PROFIBUS data link layer packets, as specified by IEC standard 61158-4-3, beginning with the start delimiter, ending with the end delimiter, and including all octets between them¶
LINKTYPE_EPON¶
259¶
Ethernet-over-passive-optical-network packets, starting with the last 6 octets of the modified preamble as specified by 65.1.3.2 Transmit in Clause 65 of Section 5 of IEEE 802.3, followed immediately by an Ethernet frame¶
LINKTYPE_IPMI_HPM_2¶
260¶
IPMI trace packets, as specified by Table 3-20 Trace Data Block Format in the PICMG HPM.2 specification The timestamps for packets in this format must match the timestamps in the Trace Data Blocks¶
LINKTYPE_WATTSTOPPER_DLM¶
263¶
WattStopper Digital Lighting Management (DLM) and Legrand Nitoo Open protocol packets¶
LINKTYPE_ISO_14443¶
264¶
ISO 14443 contactless smartcard messages¶
LINKTYPE_USB_DARWIN¶
266¶
USB packets captured on a Darwin-based operating system (macOS, etc.)¶
LINKTYPE_SDLC¶
268¶
SDLC packets, as specified by Chapter 1, DLC Links, section Synchronous Data Link Control (SDLC) of Systems Network Architecture Formats, GA27-3136-20 , without the flag fields, zero-bit insertion, or Frame Check Sequence field, containing SNA path information units (PIUs) as the payload¶
LINKTYPE_TI_LLN_SNIFFER¶
269¶
Reserved for Texas Instruments protocol sniffer¶
LINKTYPE_LORATAP¶
270¶
LoRaTap pseudo-header , followed by the payload, which is typically the PHYPayload from the LoRaWan specification¶
LINKTYPE_VSOCK¶
271¶
Protocol for communication between host and guest machines in VMware and KVM hypervisors¶
LINKTYPE_NORDIC_BLE¶
272¶
Messages to and from a Nordic Semiconductor nRF Sniffer for Bluetooth LE packets¶
LINKTYPE_DOCSIS31_XRA31¶
273¶
DOCSIS packets and bursts, preceded by a pseudo-header¶
LINKTYPE_ETHERNET_MPACKET¶
274¶
mPackets, as specified by IEEE 802.3br Figure 99-4, starting with the preamble and always ending with a CRC field¶
LINKTYPE_DISPLAYPORT_AUX¶
275¶
DisplayPort AUX channel monitoring messages¶
LINKTYPE_EBHSCR¶
279¶
Elektrobit High Speed Capture and Replay (EBHSCR) format¶
LINKTYPE_VPP_DISPATCH¶
280¶
fd.io VPP graph dispatcher trace records¶
LINKTYPE_DSA_TAG_BRCM¶
281¶
Ethernet frames, with a Broadcom switch tag inserted¶
LINKTYPE_DSA_TAG_BRCM_PREPEND¶
282¶
Ethernet frames, with a Broadcom switch tag prepended¶
LINKTYPE_IEEE802_15_4_TAP¶
283¶
IEEE 802.15.4 Low-Rate Wireless Networks, with a pseudo-header containing TLVs with metadata preceding the 802.15.4 header¶
LINKTYPE_DSA_TAG_DSA¶
284¶
Ethernet frames, with a Marvell DSA switch tag inserted¶
LINKTYPE_DSA_TAG_EDSA¶
285¶
Ethernet frames, with a Marvell EDSA switch tag inserted¶
LINKTYPE_ELEE¶
286¶
Payload of lawful intercept packets using the ELEE protocol The packet begins with the ELEE header; it does not include any transport-layer or lower-layer headers for protocols used to transport ELEE packets¶
LINKTYPE_Z_WAVE_SERIAL¶
287¶
Serial frames transmitted between a host and a Z-Wave chip over an RS-232 or USB serial connection¶
[Z_WAVE_SERIAL] section 5¶
LINKTYPE_USB_2_0¶
288¶
USB 2.0, 1.1, or 1.0 packet, beginning with a PID, as described by Chapter 8 Protocol Layer of the the Universal Serial Bus Specification Revision 2.0¶
LINKTYPE_ATSC_ALP¶
289¶
ATSC Link-Layer Protocol frames, as described in section 5 of the A/330 Link-Layer Protocol specification, found at https://www.atsc.org/atsc-documents/type/3-0-standards/, beginning with a Base Header¶
LINKTYPE_NETANALYZER_NG¶
291¶
Reserved for Hilscher Gesellschaft fuer Systemautomation mbH netANALYZER NG hardware and software¶
LINKTYPE_ZBOSS_NCP¶
292¶
ZBOSS NCP Serial Protocol, with a pseudo-header¶
LINKTYPE_USB_2_0_LOW_SPEED¶
293¶
Low-Speed USB 2.0, 1.1, or 1.0 packet, beginning with a PID, as described by Chapter 8 "Protocol Layer" of the https://www.usb.org/document-library/usb-20-specification the Universal Serial Bus Specification Revision 2.0¶
LINKTYPE_USB_2_0_FULL_SPEED¶
294¶
Full-Speed USB 2.0, 1.1, or 1.0 packet, beginning with a PID, as described by Chapter 8 "Protocol Layer" of the https://www.usb.org/document-library/usb-20-specification the Universal Serial Bus Specification Revision 2.0¶
LINKTYPE_USB_2_0_HIGH_SPEED¶
295¶
High-Speed USB 2.0 packet, beginning with a PID, as described by Chapter 8 "Protocol Layer" of the https://www.usb.org/document-library/usb-20-specification the Universal Serial Bus Specification Revision 2.0¶
LINKTYPE_AUERSWALD_LOG¶
296¶
Auerswald Logger Protocol, as described in https://github.com/Auerswald-GmbH/auerlog/blob/master/auerlog.txt¶
LINKTYPE_ZWAVE_TAP¶
297¶
Z-Wave packets, as specified by ITU-T Recommendation G.9959, with a https://gitlab.com/exegin/zwave-g9959-tap TAP meta-data header¶
LINKTYPE_SILABS_DEBUG_CHANNEL¶
298¶
Silicon Labs debug channel protocol, as described in https://github.com/SiliconLabs/java_packet_trace_library/blob/master/doc/debug-channel.md¶
LINKTYPE_FIRA_UCI¶
299¶
Ultra-wideband (UWB) controller interface protocol (UCI)¶
LINKTYPE_MDB¶
300¶
MDB (Multi-Drop Bus) protocol between a vending machine controller and peripherals inside the vending machine, with the message format specified by https://www.kaiser.cx/pcap-mdb.html the PCAP format for MDB specification¶
LINKTYPE_DECT_NR¶
301¶
DECT-2020 New Radio (NR) MAC layer specified in https://www.etsi.org/committee/1394-dect ETSI TS 103 636-4. The Physical Header Field is always encoded using 80 bits (10 bytes). Broadcast transmissions using 40 bits (5 bytes) is padded with 40 zero bits (5 bytes). When padding is used the Receiver Identity value 0x0000 (reserved address) is used to detect broadcast transmissions¶
When processing a request for a Specification Required allocation the Designated Experts are expected to be able to find the relevant specification at a clearly stable URL. It is noted that many enterprise web sites do not maintain URLs over a long period of time, and a documented in a "wp-uploaded" section is highly likely to disappear. In addition Specifications that require a reader to click through any kind of marketing or legal agreement are not considered public. (This is the opinion of other corporate lawyers, who worry about what their employees might have agreed to)¶
The specification needs to be clearly written, and when the contents of the link type can contain an IPv4 or IPv6 header, then the octets between the beginning of the link type and the IP header needs to be very clearly specified in that document.¶
Specifications that are not publicly available, but which may be obtained via liaison agreements (such as to ITU-T, 3GPP, IEEE, etc.) are acceptable particularly if the document will be public eventually, but are discouraged. For other documents, the Designated Expert will need use their judgement, or consult the WG or an Area Director.¶
Linktypes may be allocated for specifications not publicly available may be made within the First-Come/First-Served area. This includes specifications that might be classified. The minimal requirement is for a contact person for that link type.¶
This document describes the IANA registration rules for the LINKTYPE encapsulations. PCAP, and PCAPNG packet file formats use this value to determine what kind of headers precede network packet captures. Many of these formats can contain IPv4 and IPv6 packets. A system reading PCAP or PCAPNG format captures can be subject to arbitrary inputs that may be controlled by malicious entities, so utmost caution is required.¶
Many LINKTYPE formats include a "snapshot" length, which may be smaller than the actual packet. It is therefore very likely that trailing parts of a packet capture may be omitted, yet internal length fields in the packets will claim the packet is bigger than the capture. This leads to trivial buffer overreads, and systems interpreting the packets need to carefully scrutinize all attempts to read data from a capture.¶
PCAP has been developed over three and half decades by a variety of developers, including: Bill Fenner, Denis Ovsienko, Francois-Xavier Le Bail, Fulvio Risso, Gerald Combs, Gianluca Varenni, Gisle Vanem, Hannes Gredler, Joerg Mayer, Michal Sekletar, Stephen Donnelly, Torsten Landschoff, and Jun-ichiro itojun Hagino¶
PCAP was originally created at LBL by Steve McCanne, Craig Leres, and Van Jacobson.¶
The authors wish to thank: Michael Tuexen, Mohamed Boucadair, Carsten Bormann, Henk Birkholtz, and Robert Wilton their invaluable comments and encouragement.¶