idnits 2.17.1 draft-ietf-opsawg-pcap-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 25 characters in excess of 72. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (25 October 2021) is 912 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'LINKTYPES' is mentioned on line 264, but not defined == Missing Reference: 'TM' is mentioned on line 1263, but not defined == Outdated reference: A later version (-05) exists of draft-tuexen-opsawg-pcapng-04 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Harris, Ed. 3 Internet-Draft 4 Intended status: Informational M. Richardson 5 Expires: 28 April 2022 Sandelman 6 25 October 2021 8 PCAP Capture File Format 9 draft-ietf-opsawg-pcap-00 11 Abstract 13 This document describes the format used by the libpcap library to 14 record captured packets to a file. Programs using the libpcap 15 library to read and write those files, and thus reading and writing 16 files in that format, include tcpdump. 18 Discussion Venues 20 This note is to be removed before publishing as an RFC. 22 Discussion of this document takes place on the OPSAWG Working Group 23 mailing list (opsawg@ietf.org), which is archived at 24 https://mailarchive.ietf.org/arch/browse/opsawg/. 26 Source for this draft and an issue tracker can be found at 27 https://github.com/pcapng/pcapng. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at https://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on 28 April 2022. 46 Copyright Notice 48 Copyright (c) 2021 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 53 license-info) in effect on the date of publication of this document. 54 Please review these documents carefully, as they describe your rights 55 and restrictions with respect to this document. Code Components 56 extracted from this document must include Simplified BSD License text 57 as described in Section 4.e of the Trust Legal Provisions and are 58 provided without warranty as described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 3. General File Structure . . . . . . . . . . . . . . . . . . . 3 65 4. File Header . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 5. Packet Record . . . . . . . . . . . . . . . . . . . . . . . . 5 67 6. Recommended File Name Extension: .pcap . . . . . . . . . . . 7 68 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 69 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 70 8.1. Media-Type Registry . . . . . . . . . . . . . . . . . . . 7 71 8.1.1. application/pcap . . . . . . . . . . . . . . . . . . 7 72 8.2. LinkType Registry . . . . . . . . . . . . . . . . . . . . 8 73 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 34 74 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 35 75 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 35 76 11.1. Normative References . . . . . . . . . . . . . . . . . . 35 77 11.2. Informative References . . . . . . . . . . . . . . . . . 35 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 80 1. Introduction 82 In the late 1980's, Van Jacobson, Steve McCanne, and others at the 83 Network Research Group at Lawrence Berkeley National Laboratory 84 developed the tcpdump program to capture and dissect network traces. 85 The code to capture traffic, using low-level mechanisms in various 86 operating systems, and to read and write network traces to a file was 87 later put into a library named libpcap. 89 This document describes the format used by tcpdump, and other 90 programs using libpcap, to read and write network traces. 92 2. Terminology 94 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 95 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 96 "OPTIONAL" in this document are to be interpreted as described in 97 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 98 capitals, as shown here. 100 3. General File Structure 102 A capture file begins with a File Header, followed by zero or more 103 Packet Records, one per packet. 105 All fields in the File Header and in Packet Records will always be 106 saved according to the characteristics (little endian / big endian) 107 of the capturing machine. This refers to all the fields that are 108 saved as numbers and that span over two or more octets. 110 The approach of having the file saved in the native format of the 111 generating host is more efficient because it avoids translation of 112 data when reading / writing on the host itself, which is the most 113 common case when generating/processing capture captures. 115 The packets are shown in traditional IETF diagram, with the bits 116 numbered from the left to the right. The bit numbering does not 117 reflect the binary value position, as IETF protocols are 118 traditionally in big-endian network-byte order. The most significant 119 bit is therefore on the left in this diagram as if the file is being 120 stored on a big-endian system. 122 4. File Header 124 The File Header has the following format: 126 1 2 3 127 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 0 | Magic Number | 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 4 | Major Version | Minor Version | 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 8 | Reserved1 | 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 12 | Reserved2 | 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 137 16 | SnapLen | 138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 20 | FCS |f|0 0 0 0 0 0 0 0 0 0 0 0| LinkType | 140 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 Figure 1: File Header 144 The File Header length is 24 octets. 146 The meaning of the fields in the File Header is: 148 Magic Number (32 bits): an unsigned magic number, whose value is 149 either the hexadecimal number 0xA1B2C3D4 or the hexadecimal number 150 0xA1B23C4D. 152 If the value is 0xA1B2C3D4, time stamps in Packet Records (see 153 Figure 2) are in seconds and microseconds; if it is 0xA1B23C4D, 154 time stamps in Packet Records are in seconds and nanoseconds. 156 These numbers can be used to distinguish sessions that have been 157 saved on little-endian machines from the ones saved on big-endian 158 machines, and to heuristically identify pcap files. 160 Major Version (16 bits): an unsigned value, giving the number of the 161 current major version of the format. The value for the current 162 version of the format is 2. This value should change if the 163 format changes in such a way that code that reads the new format 164 could not read the old format (i.e., code to read both formats 165 would have to check the version number and use different code 166 paths for the two formats) and code that reads the old format 167 could not read the new format. 169 Minor Version (16 bits): an unsigned value, giving the number of the 170 current minor version of the format. The value is for the current 171 version of the format is 4. This value should change if the 172 format changes in such a way that code that reads the new format 173 could read the old format without checking the version number but 174 code that reads the old format could not read all files in the new 175 format. 177 Reserved1 (32 bits): not used - SHOULD be filled with 0 by pcap file 178 writers, and MUST be ignored by pcap file readers. This value was 179 documented by some older implementations as "gmt to local 180 correction". Some older pcap file writers stored non-zero values 181 in this field. 183 Reserved2 (32 bits): not used - SHOULD be filled with 0 by pcap file 184 writers, and MUST be ignored by pcap file readers. This value was 185 documented by some older implementations as "accuracy of 186 timestamps". Some older pcap file writers stored non-zero values 187 in this field. 189 SnapLen (32 bits): an unsigned value indicating the maximum number 190 of octets captured from each packet. The portion of each packet 191 that exceeds this value will not be stored in the file. This 192 value MUST NOT be zero; if no limit was specified, the value 193 should be a number greater than or equal to the largest packet 194 length in the file. 196 LinkType (16 bits): a 16-bit unsigned value that defines the link 197 layer type of packets in the file. This field is defined in the 198 Section 8.2 IANA registry. 200 Frame Cyclic Sequence (FCS) present (4 bits): if the "f" bit is set, 201 then the 3 FCS bits provide the number of 16-bit (2 byte) words of 202 FCS that are appended to each packet. 204 valid values are between 0 and 7, with ethernet typically having a 205 length of 4 bytes, or a value of 2. 207 The bits marked as zero MUST be set to zero by pcap writers, and MUST 208 be ignored by pcap readers. 210 5. Packet Record 212 A Packet Record is the standard container for storing the packets 213 coming from the network. 215 1 2 3 216 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 0 | Timestamp (Seconds) | 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 4 | Timestamp (Microseconds or nanoseconds) | 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 8 | Captured Packet Length | 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 12 | Original Packet Length | 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 226 16 / / 227 / Packet Data / 228 / variable length / 229 / / 230 +---------------------------------------------------------------+ 232 Figure 2: Packet Record 234 The Packet Header length is 16 octets. 236 The meaning of the fields in the Packet Record is: 238 Timestamp (Seconds) and Timestamp (Microseconds or nanoseconds): sec 239 onds and fraction of a seconds values of a timestamp. 241 The seconds value is a 32-bit unsigned integer that represents the 242 number of seconds that have elapsed since 1970-01-01 00:00:00 UTC, 243 and the microseconds or nanoseconds value represents the number of 244 microseconds or nanoseconds that have elapsed since that seconds. 246 Whether the value represents microseconds or nanoseconds is 247 specified by the magic number in the File Header. 249 Captured Packet Length (32 bits): an unsigned value that indicates 250 the number of octets captured from the packet (i.e. the length of 251 the Packet Data field). It will be the minimum value among the 252 Original Packet Length and the snapshot length for the interface 253 (SnapLen, defined in Figure 1). 255 Original Packet Length (32 bits): an unsigned value that indicates 256 the actual length of the packet when it was transmitted on the 257 network. It can be different from the Captured Packet Length if 258 the packet has been truncated by the capture process. 260 Packet Data: the data coming from the network, including link-layer 261 headers. The actual length of this field is Captured Packet 262 Length. The format of the link-layer headers depends on the 263 LinkType field specified in the file header (see Figure 1) and it 264 is specified in the entry for that format in [LINKTYPES]. 266 6. Recommended File Name Extension: .pcap 268 The recommended file name extension for the "PCAP Capture File 269 Format" specified in this document is ".pcap". 271 On Windows and macOS, files are distinguished by an extension to 272 their filename. Such an extension is technically not actually 273 required, as applications should be able to automatically detect the 274 pcap file format through the "magic bytes" at the beginning of the 275 file, as some other UN*X desktop environments do. However, using 276 name extensions makes it easier to work with files (e.g. visually 277 distinguish file formats) so it is recommended - though not required 278 - to use .pcap as the name extension for files following this 279 specification. 281 Please note: To avoid confusion (such as the current usage of .cap 282 for a plethora of different capture file formats) file name 283 extensions other than .pcap should be avoided. 285 There is new work to create the PCAP Next Generation capture File 286 Format (see [I-D.tuexen-opsawg-pcapng]). The new file format is not 287 compatible with this specification, but many programs read both 288 transparently. Files of that type will usually start with a 289 Section Header Block, with a magic number of 0x0A0D0D0A. 291 7. Security Considerations 293 TBD. 295 8. IANA Considerations 297 This document requires the following IANA actions: 299 8.1. Media-Type Registry 301 This section registers the the 'application/pcap' in the "Media 302 Types" registry. These media types are used to indicate that the 303 content is packet capture as described in this document. 305 8.1.1. application/pcap 306 Type name: application 307 Subtype name: pcap 308 Required parameters: none 309 Optional parameters: none 310 Encoding considerations: PCAP files contain network packets 311 Security considerations: See Security Considerations, Section 312 Interoperability considerations: The format is designed to be broadly interoperable. 313 Published specification: THIS RFC. 314 Applications that use this media type: tcpdump, wireshark, others. 315 Additional information: 316 Magic number(s): 0xA1B2C3D4, and 0xA1B23C4D in both endian orders 317 File extension(s): .pcap 318 Macintosh file type code(s): none 319 Person & email address to contact for further information: The Tcpdump Group, www.tcpdump.org 320 Intended usage: LIMITED 321 Restrictions on usage: NONE 322 Author: Guy Harris and Michael Richardson 323 Change controller: The Tcpdump Group 324 Provisional registration? (standards tree only): NO 326 8.2. LinkType Registry 328 IANA is requested to create a new Registry entitled: "The PCAP 329 Registry", and within that Registry to create a table called: "PCAP 330 LinkType List". 332 The LinkType Registry is a table of 16-bit numbers. The Registry has 333 three sections with different [RFC8126] rules: 335 * values from 0 to 32767 are marked as Specification Required. 337 * values from 32768 to 65000 are marked as First-Come First-Served. 339 * values from 65000 to 65535 are marked as Private Use. 341 The Registry has four columns: the symbolic name 342 (LINKTYPE_something), the integer value, a very short description, 343 and the document/requestor reference. 345 The Registry shall be populated as follows in the table below. In 346 each case here, the reference should be http://www.tcpdump.org/ 347 linktypes.html, which is not repeated. 349 The initial value of table is base upon the Link type list maintained 350 by libpcap, and published on the tcpdump.org web site as 351 http://www.tcpdump.org/linktypes.html. 353 There is often an associated DLT value which are often identical in 354 value, but not universally so. DLT values are associated with 355 specific operation system captures, and are operating system 356 specific. 358 +=====================================+========+====================+ 359 | LINKTYPE name |LINKTYPE|description | 360 | | value | | 361 +=====================================+========+====================+ 362 | LINKTYPE_NULL | 0 |BSD loopback | 363 | | |encapsulation | 364 +-------------------------------------+--------+--------------------+ 365 | LINKTYPE_ETHERNET | 1 |IEEE 802.3 Ethernet | 366 +-------------------------------------+--------+--------------------+ 367 | LINKTYPE_EXP_ETHERNET | 2 |Xerox experimental | 368 | | |3Mb Ethernet | 369 +-------------------------------------+--------+--------------------+ 370 | LINKTYPE_AX25 | 3 |AX.25 packet | 371 +-------------------------------------+--------+--------------------+ 372 | LINKTYPE_PRONET | 4 |Reserved for PRONET | 373 +-------------------------------------+--------+--------------------+ 374 | LINKTYPE_CHAOS | 5 |Reserved for MIT | 375 | | |CHAOSNET | 376 +-------------------------------------+--------+--------------------+ 377 | LINKTYPE_IEEE802_5 | 6 |IEEE 802.5 Token | 378 | | |Ring | 379 +-------------------------------------+--------+--------------------+ 380 | LINKTYPE_ARCNET_BSD | 7 |ARCNET Data Packets | 381 | | |with BSD | 382 | | |encapsulation | 383 +-------------------------------------+--------+--------------------+ 384 | LINKTYPE_SLIP | 8 |SLIP, w/ | 385 | | |LINKTYPE_SLIP | 386 | | |header. | 387 +-------------------------------------+--------+--------------------+ 388 | LINKTYPE_PPP | 9 |PPP, as per RFC | 389 | | |1661/RFC 1662 | 390 +-------------------------------------+--------+--------------------+ 391 | LINKTYPE_FDDI | 10 |FDDI: per ANSI | 392 | | |INCITS 239-1994. | 393 +-------------------------------------+--------+--------------------+ 394 | not to be used | 11-49 |Do not use these | 395 | | |values | 396 +-------------------------------------+--------+--------------------+ 397 | LINKTYPE_PPP_HDLC | 50 |PPP in HDLC-like | 398 | | |framing, as per RFC | 399 | | |1662 | 400 +-------------------------------------+--------+--------------------+ 401 | LINKTYPE_PPP_ETHER | 51 |PPPoE; per RFC 2516 | 402 +-------------------------------------+--------+--------------------+ 403 | not to be used | 52-98 |Do not use these | 404 | | |values | 405 +-------------------------------------+--------+--------------------+ 406 | LINKTYPE_SYMANTEC_FIREWALL | 99 |Reserved for | 407 | | |Symantec Enterprise | 408 | | |Firewall | 409 +-------------------------------------+--------+--------------------+ 410 | LINKTYPE_ATM_RFC1483 | 100 |RFC 1483 LLC/SNAP- | 411 | | |encapsulated ATM | 412 +-------------------------------------+--------+--------------------+ 413 | LINKTYPE_RAW | 101 |Raw IP; begins with | 414 | | |an IPv4 or IPv6 | 415 | | |header | 416 +-------------------------------------+--------+--------------------+ 417 | LINKTYPE_SLIP_BSDOS | 102 |Reserved for BSD/OS | 418 | | |SLIP BPF header | 419 +-------------------------------------+--------+--------------------+ 420 | LINKTYPE_PPP_BSDOS | 103 |Reserved for BSD/OS | 421 | | |PPP BPF header | 422 +-------------------------------------+--------+--------------------+ 423 | LINKTYPE_C_HDLC | 104 |Cisco PPP with HDLC | 424 | | |framing, as per | 425 | | |section 4.3.1 of RFC| 426 | | |1547 | 427 +-------------------------------------+--------+--------------------+ 428 | LINKTYPE_IEEE802_11 | 105 |IEEE 802.11 wireless| 429 | | |LAN. | 430 +-------------------------------------+--------+--------------------+ 431 | LINKTYPE_ATM_CLIP | 106 |ATM Classical IP, | 432 | | |with no header | 433 | | |preceding IP | 434 +-------------------------------------+--------+--------------------+ 435 | LINKTYPE_FRELAY | 107 |Frame Relay LAPF | 436 | | |frames | 437 +-------------------------------------+--------+--------------------+ 438 | LINKTYPE_LOOP | 108 |OpenBSD loopback | 439 | | |encapsulation | 440 +-------------------------------------+--------+--------------------+ 441 | LINKTYPE_ENC | 109 |Reserved for OpenBSD| 442 | | |IPSEC encapsulation | 443 +-------------------------------------+--------+--------------------+ 444 | LINKTYPE_LANE8023 | 110 |Reserved for ATM | 445 | | |LANE + 802.3 | 446 +-------------------------------------+--------+--------------------+ 447 | LINKTYPE_HIPPI | 111 |Reserved for NetBSD | 448 | | |HIPPI | 449 +-------------------------------------+--------+--------------------+ 450 | LINKTYPE_HDLC | 112 |Reserved for NetBSD | 451 | | |HDLC framing | 452 +-------------------------------------+--------+--------------------+ 453 | LINKTYPE_LINUX_SLL | 113 |Linux "cooked" | 454 | | |capture | 455 | | |encapsulation | 456 +-------------------------------------+--------+--------------------+ 457 | LINKTYPE_LTALK | 114 |Apple LocalTalk | 458 +-------------------------------------+--------+--------------------+ 459 | LINKTYPE_ECONET | 115 |Reserved for Acorn | 460 | | |Econet | 461 +-------------------------------------+--------+--------------------+ 462 | LINKTYPE_IPFILTER | 116 |Reserved for OpenBSD| 463 | | |ipfilter | 464 +-------------------------------------+--------+--------------------+ 465 | LINKTYPE_PFLOG | 117 |OpenBSD pflog; | 466 | | |"struct pfloghdr" | 467 | | |structure | 468 +-------------------------------------+--------+--------------------+ 469 | LINKTYPE_CISCO_IOS | 118 |Reserved for Cisco- | 470 | | |internal use | 471 +-------------------------------------+--------+--------------------+ 472 | LINKTYPE_IEEE802_11_PRISM | 119 |Prism monitor mode | 473 +-------------------------------------+--------+--------------------+ 474 | LINKTYPE_IEEE802_11_AIRONET | 120 |Reserved for 802.11 | 475 | | |+ FreeFreeBSD | 476 | | |Aironet radio | 477 | | |metadata | 478 +-------------------------------------+--------+--------------------+ 479 | LINKTYPE_HHDLC | 121 |Reserved for Siemens| 480 | | |HiPath HDLC | 481 +-------------------------------------+--------+--------------------+ 482 | LINKTYPE_IP_OVER_FC | 122 |RFC 2625 IP-over- | 483 | | |Fibre Channel | 484 +-------------------------------------+--------+--------------------+ 485 | LINKTYPE_SUNATM | 123 |ATM traffic, / per | 486 | | |SunATM devices | 487 +-------------------------------------+--------+--------------------+ 488 | LINKTYPE_RIO | 124 |Reserved for RapidIO| 489 +-------------------------------------+--------+--------------------+ 490 | LINKTYPE_PCI_EXP | 125 |Reserved for PCI | 491 | | |Express | 492 +-------------------------------------+--------+--------------------+ 493 | LINKTYPE_AURORA | 126 |Reserved for Xilinx | 494 | | |Aurora link layer | 495 +-------------------------------------+--------+--------------------+ 496 | LINKTYPE_IEEE802_11_RADIOTAP | 127 |Radiotap | 497 | | |header[Radiotap], | 498 | | |followed by an | 499 | | |802.11 header | 500 +-------------------------------------+--------+--------------------+ 501 | LINKTYPE_TZSP | 128 |Reserved for Tazmen | 502 | | |Sniffer Protocol | 503 +-------------------------------------+--------+--------------------+ 504 | LINKTYPE_ARCNET_LINUX | 129 |ARCNET Data Packets,| 505 | | |per RFC 1051 frames | 506 | | |w/variations | 507 +-------------------------------------+--------+--------------------+ 508 | LINKTYPE_JUNIPER_MLPPP | 130 |Reserved for Juniper| 509 | | |Networks | 510 +-------------------------------------+--------+--------------------+ 511 | LINKTYPE_JUNIPER_MLFR | 131 |Reserved for Juniper| 512 | | |Networks | 513 +-------------------------------------+--------+--------------------+ 514 | LINKTYPE_JUNIPER_ES | 132 |Reserved for Juniper| 515 | | |Networks | 516 +-------------------------------------+--------+--------------------+ 517 | LINKTYPE_JUNIPER_GGSN | 133 |Reserved for Juniper| 518 | | |Networks | 519 +-------------------------------------+--------+--------------------+ 520 | LINKTYPE_JUNIPER_MFR | 134 |Reserved for Juniper| 521 | | |Networks | 522 +-------------------------------------+--------+--------------------+ 523 | LINKTYPE_JUNIPER_ATM2 | 135 |Reserved for Juniper| 524 | | |Networks | 525 +-------------------------------------+--------+--------------------+ 526 | LINKTYPE_JUNIPER_SERVICES | 136 |Reserved for Juniper| 527 | | |Networks | 528 +-------------------------------------+--------+--------------------+ 529 | LINKTYPE_JUNIPER_ATM1 | 137 |Reserved for Juniper| 530 | | |Networks | 531 +-------------------------------------+--------+--------------------+ 532 | LINKTYPE_APPLE_IP_OVER_IEEE1394 | 138 |Apple IP-over-IEEE | 533 | | |1394 cooked header | 534 +-------------------------------------+--------+--------------------+ 535 | LINKTYPE_MTP2_WITH_PHDR | 139 |Signaling System 7 | 536 | | |(SS7) Message | 537 | | |Transfer Part Level | 538 | | |ITU-T Q.703 | 539 +-------------------------------------+--------+--------------------+ 540 | LINKTYPE_MTP2 | 140 |SS7 Level 2, Q.703 | 541 +-------------------------------------+--------+--------------------+ 542 | LINKTYPE_MTP3 | 141 |SS7 Level 3, Q.704 | 543 +-------------------------------------+--------+--------------------+ 544 | LINKTYPE_SCCP | 142 |SS7 Control Part, | 545 | | |ITU-T | 546 | | |Q.711/Q.712/Q.713/ | 547 | | |Q.714 | 548 +-------------------------------------+--------+--------------------+ 549 | LINKTYPE_DOCSIS | 143 |DOCSIS MAC frames, | 550 | | |DOCSIS 3.1 | 551 +-------------------------------------+--------+--------------------+ 552 | LINKTYPE_LINUX_IRDA | 144 |Linux-IrDA packets | 553 | | |w/ | 554 | | |LINKTYPE_LINUX_IRDA | 555 | | |header | 556 +-------------------------------------+--------+--------------------+ 557 | LINKTYPE_IBM_SP | 145 |Reserved for IBM SP | 558 | | |switch | 559 +-------------------------------------+--------+--------------------+ 560 | LINKTYPE_IBM_SN | 146 |Reserved for IBM | 561 | | |Next Federation | 562 | | |switch | 563 +-------------------------------------+--------+--------------------+ 564 | LINKTYPE_RESERVED_01 | 147 |For private use | 565 +-------------------------------------+--------+--------------------+ 566 | LINKTYPE_RESERVED_02 | 148 |For private use | 567 +-------------------------------------+--------+--------------------+ 568 | LINKTYPE_RESERVED_03 | 149 |For private use | 569 +-------------------------------------+--------+--------------------+ 570 | LINKTYPE_RESERVED_04 | 150 |For private use | 571 +-------------------------------------+--------+--------------------+ 572 | LINKTYPE_RESERVED_05 | 151 |For private use | 573 +-------------------------------------+--------+--------------------+ 574 | LINKTYPE_RESERVED_06 | 152 |For private use | 575 +-------------------------------------+--------+--------------------+ 576 | LINKTYPE_RESERVED_07 | 153 |For private use | 577 +-------------------------------------+--------+--------------------+ 578 | LINKTYPE_RESERVED_08 | 154 |For private use | 579 +-------------------------------------+--------+--------------------+ 580 | LINKTYPE_RESERVED_09 | 155 |For private use | 581 +-------------------------------------+--------+--------------------+ 582 | LINKTYPE_RESERVED_10 | 156 |For private use | 583 +-------------------------------------+--------+--------------------+ 584 | LINKTYPE_RESERVED_11 | 157 |For private use | 585 +-------------------------------------+--------+--------------------+ 586 | LINKTYPE_RESERVED_12 | 158 |For private use | 587 +-------------------------------------+--------+--------------------+ 588 | LINKTYPE_RESERVED_13 | 159 |For private use | 589 +-------------------------------------+--------+--------------------+ 590 | LINKTYPE_RESERVED_14 | 160 |For private use | 591 +-------------------------------------+--------+--------------------+ 592 | LINKTYPE_RESERVED_15 | 161 |For private use | 593 +-------------------------------------+--------+--------------------+ 594 | LINKTYPE_RESERVED_16 | 162 |For private use | 595 +-------------------------------------+--------+--------------------+ 596 | LINKTYPE_IEEE802_11_AVS | 163 |AVS header[AVS], | 597 | | |followed by an | 598 | | |802.11 header | 599 +-------------------------------------+--------+--------------------+ 600 | LINKTYPE_JUNIPER_MONITOR | 164 |Reserved for Juniper| 601 | | |Networks | 602 +-------------------------------------+--------+--------------------+ 603 | LINKTYPE_BACNET_MS_TP | 165 |BACnet MS/TP frames,| 604 | | |per 9.3 MS/TP Frame | 605 | | |Format ANSI 135 | 606 +-------------------------------------+--------+--------------------+ 607 | LINKTYPE_PPP_PPPD | 166 |PPP in HDLC-like | 608 | | |encapsulation, like | 609 | | |LINKTYPE_PPP_HDLC, | 610 | | |different stuffing | 611 +-------------------------------------+--------+--------------------+ 612 | LINKTYPE_JUNIPER_PPPOE | 167 |Reserved for Juniper| 613 | | |Networks | 614 +-------------------------------------+--------+--------------------+ 615 | LINKTYPE_JUNIPER_PPPOE_ATM | 168 |Reserved for Juniper| 616 | | |Networks | 617 +-------------------------------------+--------+--------------------+ 618 | LINKTYPE_GPRS_LLC | 169 |General Packet Radio| 619 | | |Service Logical Link| 620 | | |Control, as per 3GPP| 621 | | |TS 04.64 | 622 +-------------------------------------+--------+--------------------+ 623 | LINKTYPE_GPF_T | 170 |Transparent-mapped | 624 | | |generic framing | 625 | | |procedure, as | 626 | | |specified by ITU-T | 627 | | |Recommendation | 628 | | |G.7041/Y.1303 | 629 +-------------------------------------+--------+--------------------+ 630 | LINKTYPE_GPF_F | 171 |Frame-mapped generic| 631 | | |framing procedure, | 632 | | |as specified by | 633 | | |ITU-T Recommendation| 634 | | |G.7041/Y.1303 | 635 +-------------------------------------+--------+--------------------+ 636 | LINKTYPE_GCOM_T1E1 | 172 |Reserved for Gcom | 637 | | |T1/E1 line | 638 | | |monitoring equipment| 639 +-------------------------------------+--------+--------------------+ 640 | LINKTYPE_GCOM_SERIAL | 173 |Reserved for Gcom | 641 | | |T1/E1 line | 642 | | |monitoring equipment| 643 +-------------------------------------+--------+--------------------+ 644 | LINKTYPE_JUNIPER_PIC_PEER | 174 |Reserved for Juniper| 645 | | |Networks | 646 +-------------------------------------+--------+--------------------+ 647 | LINKTYPE_ERF_ETH | 175 |Endace ERF header | 648 | | |followed by 802.3 | 649 | | |Ethernet | 650 +-------------------------------------+--------+--------------------+ 651 | LINKTYPE_ERF_POS | 176 |Endace ERF header | 652 | | |followed by Packet- | 653 | | |over-SONET | 654 +-------------------------------------+--------+--------------------+ 655 | LINKTYPE_LINUX_LAPD | 177 |Link Access | 656 | | |Procedures on the D | 657 | | |Channel (LAPD) | 658 | | |frames, as specified| 659 | | |by ITU-T | 660 | | |Recommendation Q.920| 661 | | |and ITU-T | 662 | | |Recommendation Q.921| 663 | | |, captured via | 664 | | |vISDN, with a | 665 | | |LINKTYPE_LINUX_LAPD | 666 | | |header , followed by| 667 | | |the Q.921 frame, | 668 | | |starting with the | 669 | | |address field. | 670 +-------------------------------------+--------+--------------------+ 671 | LINKTYPE_JUNIPER_ETHER | 178 |Reserved for Juniper| 672 | | |Networks | 673 +-------------------------------------+--------+--------------------+ 674 | LINKTYPE_JUNIPER_PPP | 179 |Reserved for Juniper| 675 | | |Networks | 676 +-------------------------------------+--------+--------------------+ 677 | LINKTYPE_JUNIPER_FRELAY | 180 |Reserved for Juniper| 678 | | |Networks | 679 +-------------------------------------+--------+--------------------+ 680 | LINKTYPE_JUNIPER_CHDLC | 181 |Reserved for Juniper| 681 | | |Networks | 682 +-------------------------------------+--------+--------------------+ 683 | LINKTYPE_MFR | 182 |FRF.16.1 Multi-Link | 684 | | |Frame Relay frames, | 685 | | |beginning with an | 686 | | |FRF.12 Interface | 687 | | |fragmentation format| 688 | | |fragmentation | 689 | | |header. | 690 +-------------------------------------+--------+--------------------+ 691 | LINKTYPE_JUNIPER_VP | 182 |Reserved for Juniper| 692 | | |Networks | 693 +-------------------------------------+--------+--------------------+ 694 | LINKTYPE_A653_ICM | 185 |Reserved for Arinc | 695 | | |653 Interpartition | 696 | | |Communication | 697 | | |messages | 698 +-------------------------------------+--------+--------------------+ 699 | LINKTYPE_USB_FREEBSD | 186 |USB packets, | 700 | | |beginning with a | 701 | | |FreeBSD USB header | 702 +-------------------------------------+--------+--------------------+ 703 | LINKTYPE_BLUETOOTH_HCI_H4 | 187 |Bluetooth HCI UART | 704 | | |transport layer; the| 705 | | |frame contains an | 706 | | |HCI packet indicator| 707 | | |byte, as specified | 708 | | |by the UART | 709 | | |Transport Layer | 710 | | |portion of the most | 711 | | |recent Bluetooth | 712 | | |Core specification ,| 713 | | |followed by an HCI | 714 | | |packet of the | 715 | | |specified packet | 716 | | |type, as specified | 717 | | |by the Host | 718 | | |Controller Interface| 719 | | |Functional | 720 | | |Specification | 721 | | |portion of the most | 722 | | |recent Bluetooth | 723 | | |Core Specification. | 724 +-------------------------------------+--------+--------------------+ 725 | LINKTYPE_IEEE802_16_MAC_CPS | 188 |Reserved for IEEE | 726 | | |802.16 MAC Common | 727 | | |Part Sublayer | 728 +-------------------------------------+--------+--------------------+ 729 | LINKTYPE_USB_LINUX | 189 |USB packets, | 730 | | |beginning with a | 731 | | |Linux USB header, as| 732 | | |specified by the | 733 | | |struct usbmon_packet| 734 | | |in the | 735 | | |Documentation/usb/ | 736 | | |usbmon.txt file in | 737 | | |the Linux source | 738 | | |tree. Only the | 739 | | |first 48 bytes of | 740 | | |that header are | 741 | | |present. All fields| 742 | | |in the header are in| 743 | | |host byte order. | 744 | | |When performing a | 745 | | |live capture, the | 746 | | |host byte order is | 747 | | |the byte order of | 748 | | |the machine on which| 749 | | |the packets are | 750 | | |captured. When | 751 | | |reading a pcap file,| 752 | | |the byte order is | 753 | | |the byte order for | 754 | | |the file, as | 755 | | |specified by the | 756 | | |file's magic number;| 757 | | |when reading a | 758 | | |pcapng file, the | 759 | | |byte order is the | 760 | | |byte order for the | 761 | | |section of the | 762 | | |pcapng file, as | 763 | | |specified by the | 764 | | |Section Header | 765 | | |Block. | 766 +-------------------------------------+--------+--------------------+ 767 | LINKTYPE_CAN20B | 190 |Reserved for | 768 | | |Controller Area | 769 | | |Network (CAN) v. | 770 | | |2.0B packets | 771 +-------------------------------------+--------+--------------------+ 772 | LINKTYPE_IEEE802_15_4_LINUX | 191 |IEEE 802.15.4, with | 773 | | |address fields | 774 | | |padded, as is done | 775 | | |by Linux drivers | 776 +-------------------------------------+--------+--------------------+ 777 | LINKTYPE_PPI | 192 |Per-Packet | 778 | | |Information | 779 | | |information, as | 780 | | |specified by the | 781 | | |Per-Packet | 782 | | |Information Header | 783 | | |Specification , | 784 | | |followed by a packet| 785 | | |with the LINKTYPE_ | 786 | | |value specified by | 787 | | |the pph_dlt field of| 788 | | |that header. | 789 +-------------------------------------+--------+--------------------+ 790 | LINKTYPE_IEEE802_16_MAC_CPS_RADIO | 193 |Reserved for 802.16 | 791 | | |MAC Common Part | 792 | | |Sublayer plus radio | 793 | | |header | 794 +-------------------------------------+--------+--------------------+ 795 | LINKTYPE_JUNIPER_ISM | 194 |Reserved for Juniper| 796 | | |Networks | 797 +-------------------------------------+--------+--------------------+ 798 | LINKTYPE_IEEE802_15_4_WITHFCS | 195 |IEEE 802.15.4 Low- | 799 | | |Rate Wireless | 800 | | |Networks, with each | 801 | | |packet having the | 802 | | |FCS at the end of | 803 | | |the frame. | 804 +-------------------------------------+--------+--------------------+ 805 | LINKTYPE_SITA | 196 |Various link-layer | 806 | | |types, with a | 807 | | |pseudo-header , for | 808 | | |SITA | 809 +-------------------------------------+--------+--------------------+ 810 | LINKTYPE_ERF | 197 |Various link-layer | 811 | | |types, with a | 812 | | |pseudo-header, for | 813 | | |Endace DAG cards; | 814 | | |encapsulates Endace | 815 | | |ERF records. | 816 +-------------------------------------+--------+--------------------+ 817 | LINKTYPE_RAIF1 | 198 |Reserved for | 818 | | |Ethernet packets | 819 | | |captured from a u10 | 820 | | |Networks board | 821 +-------------------------------------+--------+--------------------+ 822 | LINKTYPE_IPMB_KONTRON | 199 |Reserved for IPMB | 823 | | |packet for IPMI, | 824 | | |with a 2-byte header| 825 +-------------------------------------+--------+--------------------+ 826 | LINKTYPE_JUNIPER_ST | 200 |Reserved for Juniper| 827 | | |Networks | 828 +-------------------------------------+--------+--------------------+ 829 | LINKTYPE_BLUETOOTH_HCI_H4_WITH_PHDR | 201 |Bluetooth HCI UART | 830 | | |transport layer; the| 831 | | |frame contains a | 832 | | |4-byte direction | 833 | | |field, in network | 834 | | |byte order (big- | 835 | | |endian), the low- | 836 | | |order bit of which | 837 | | |is set if the frame | 838 | | |was sent from the | 839 | | |host to the | 840 | | |controller and clear| 841 | | |if the frame was | 842 | | |received by the host| 843 | | |from the controller,| 844 | | |followed by an HCI | 845 | | |packet indicator | 846 | | |byte, as specified | 847 | | |by the UART | 848 | | |Transport Layer | 849 | | |portion of the most | 850 | | |recent Bluetooth | 851 | | |Core specification ,| 852 | | |followed by an HCI | 853 | | |packet of the | 854 | | |specified packet | 855 | | |type, as specified | 856 | | |by the Host | 857 | | |Controller Interface| 858 | | |Functional | 859 | | |Specification | 860 | | |portion of the most | 861 | | |recent Bluetooth | 862 | | |Core Specification. | 863 +-------------------------------------+--------+--------------------+ 864 | LINKTYPE_AX25_KISS | 202 |AX.25 packet, with a| 865 | | |1-byte KISS header | 866 | | |containing a type | 867 | | |indicator. | 868 +-------------------------------------+--------+--------------------+ 869 | LINKTYPE_LAPD | 203 |Link Access | 870 | | |Procedures on the D | 871 | | |Channel (LAPD) | 872 | | |frames, as specified| 873 | | |by ITU-T | 874 | | |Recommendation Q.920| 875 | | |and ITU-T | 876 | | |Recommendation Q.921| 877 | | |, starting with the | 878 | | |address field, with | 879 | | |no pseudo-header. | 880 +-------------------------------------+--------+--------------------+ 881 | LINKTYPE_PPP_WITH_DIR | 204 |PPP, as per RFC 1661| 882 | | |and RFC 1662 , | 883 | | |preceded with a one-| 884 | | |byte pseudo-header | 885 | | |with a zero value | 886 | | |meaning received by | 887 | | |this host and a non-| 888 | | |zero value meaning | 889 | | |sent by this host; | 890 | | |if the first 2 bytes| 891 | | |are 0xff and 0x03, | 892 | | |it's PPP in HDLC- | 893 | | |like framing, with | 894 | | |the PPP header | 895 | | |following those two | 896 | | |bytes, otherwise | 897 | | |it's PPP without | 898 | | |framing, and the | 899 | | |packet begins with | 900 | | |the PPP header. The| 901 | | |data in the frame is| 902 | | |not octet-stuffed or| 903 | | |bit-stuffed. | 904 +-------------------------------------+--------+--------------------+ 905 | LINKTYPE_C_HDLC_WITH_DIR | 205 |Cisco PPP with HDLC | 906 | | |framing, as per | 907 | | |section 4.3.1 of RFC| 908 | | |1547 , preceded with| 909 | | |a one-byte pseudo- | 910 | | |header with a zero | 911 | | |value meaning | 912 | | |received by this | 913 | | |host and a non-zero | 914 | | |value meaning sent | 915 | | |by this host. | 916 +-------------------------------------+--------+--------------------+ 917 | LINKTYPE_FRELAY_WITH_DIR | 206 |Frame Relay LAPF | 918 | | |frames, beginning | 919 | | |with a one-byte | 920 | | |pseudo-header with a| 921 | | |zero value meaning | 922 | | |received by this | 923 | | |host (DCE->DTE) and | 924 | | |a non-zero value | 925 | | |meaning sent by this| 926 | | |host (DTE->DCE), | 927 | | |followed by an ITU-T| 928 | | |Recommendation Q.922| 929 | | |LAPF header starting| 930 | | |with the address | 931 | | |field, and without | 932 | | |an FCS at the end of| 933 | | |the frame. | 934 +-------------------------------------+--------+--------------------+ 935 | LINKTYPE_LAPB_WITH_DIR | 207 |Link Access | 936 | | |Procedure, Balanced | 937 | | |(LAPB), as specified| 938 | | |by ITU-T | 939 | | |Recommendation X.25 | 940 | | |, preceded with a | 941 | | |one-byte pseudo- | 942 | | |header with a zero | 943 | | |value meaning | 944 | | |received by this | 945 | | |host (DCE->DTE) and | 946 | | |a non-zero value | 947 | | |meaning sent by this| 948 | | |host (DTE->DCE). | 949 +-------------------------------------+--------+--------------------+ 950 | Reserved | 208 |Reserved for an | 951 | | |unspecified link- | 952 | | |layer type | 953 +-------------------------------------+--------+--------------------+ 954 | LINKTYPE_IPMB_LINUX | 209 |IPMB over an I2C | 955 | | |circuit, with a | 956 | | |Linux-specific | 957 | | |pseudo-header | 958 +-------------------------------------+--------+--------------------+ 959 | LINKTYPE_FLEXRAY | 210 |Reserved for FlexRay| 960 | | |automotive bus | 961 +-------------------------------------+--------+--------------------+ 962 | LINKTYPE_MOST | 211 |Reserved for Media | 963 | | |Oriented Systems | 964 | | |Transport (MOST) bus| 965 +-------------------------------------+--------+--------------------+ 966 | LINKTYPE_LIN | 212 |Reserved for Local | 967 | | |Interconnect Network| 968 | | |(LIN) bus for | 969 | | |vehicle networks | 970 +-------------------------------------+--------+--------------------+ 971 | LINKTYPE_X2E_SERIAL | 213 |Reserved for X2E | 972 | | |serial line captures| 973 +-------------------------------------+--------+--------------------+ 974 | LINKTYPE_X2E_XORAYA | 214 |Reserved for X2E | 975 | | |Xoraya data loggers | 976 +-------------------------------------+--------+--------------------+ 977 | LINKTYPE_IEEE802_15_4_NONASK_PHY | 215 |IEEE 802.15.4 Low- | 978 | | |Rate Wireless | 979 | | |Networks, with each | 980 | | |packet having the | 981 | | |FCS at the end of | 982 | | |the frame, and with | 983 | | |the PHY-level data | 984 | | |for the O-QPSK, | 985 | | |BPSK, GFSK, MSK, and| 986 | | |RCC DSS BPSK PHYs (4| 987 | | |octets of 0 as | 988 | | |preamble, one octet | 989 | | |of SFD, one octet of| 990 | | |frame length + | 991 | | |reserved bit) | 992 | | |preceding the MAC- | 993 | | |layer data (starting| 994 | | |with the frame | 995 | | |control field). | 996 +-------------------------------------+--------+--------------------+ 997 | LINKTYPE_LINUX_EVDEV | 216 |Reserved for Linux | 998 | | |evdev messages | 999 +-------------------------------------+--------+--------------------+ 1000 | LINKTYPE_GSMTAP_UM | 217 |Reserved for GSM Um | 1001 | | |interface, with | 1002 | | |gsmtap header | 1003 +-------------------------------------+--------+--------------------+ 1004 | LINKTYPE_GSMTAP_ABIS | 218 |Reserved for GSM | 1005 | | |Abis interface, with| 1006 | | |gsmtap header | 1007 +-------------------------------------+--------+--------------------+ 1008 | LINKTYPE_MPLS | 219 |MPLS packets with | 1009 | | |MPLS label as the | 1010 | | |header | 1011 +-------------------------------------+--------+--------------------+ 1012 | LINKTYPE_USB_LINUX_MMAPPED | 220 |USB packets, | 1013 | | |beginning with a | 1014 | | |Linux USB header, as| 1015 | | |specified by the | 1016 | | |struct usbmon_packet| 1017 | | |in the | 1018 | | |Documentation/usb/ | 1019 | | |usbmon.txt file in | 1020 | | |the Linux source | 1021 | | |tree. All 64 bytes | 1022 | | |of the header are | 1023 | | |present. All fields| 1024 | | |in the header are in| 1025 | | |host byte order. | 1026 | | |When performing a | 1027 | | |live capture, the | 1028 | | |host byte order is | 1029 | | |the byte order of | 1030 | | |the machine on which| 1031 | | |the packets are | 1032 | | |captured. When | 1033 | | |reading a pcap file,| 1034 | | |the byte order is | 1035 | | |the byte order for | 1036 | | |the file, as | 1037 | | |specified by the | 1038 | | |file's magic number;| 1039 | | |when reading a | 1040 | | |pcapng file, the | 1041 | | |byte order is the | 1042 | | |byte order for the | 1043 | | |section of the | 1044 | | |pcapng file, as | 1045 | | |specified by the | 1046 | | |Section Header | 1047 | | |Block. For | 1048 | | |isochronous | 1049 | | |transfers, the ndesc| 1050 | | |field specifies the | 1051 | | |number of | 1052 | | |isochronous | 1053 | | |descriptors that | 1054 | | |follow. | 1055 +-------------------------------------+--------+--------------------+ 1056 | LINKTYPE_DECT | 221 |Reserved for DECT | 1057 | | |packets, with a | 1058 | | |pseudo-header | 1059 +-------------------------------------+--------+--------------------+ 1060 | LINKTYPE_AOS | 222 |Reserved for OS | 1061 | | |Space Data Link | 1062 | | |Protocol | 1063 +-------------------------------------+--------+--------------------+ 1064 | LINKTYPE_WIHART | 223 |Reserved for | 1065 | | |Wireless HART | 1066 | | |(Highway Addressable| 1067 | | |Remote Transducer) | 1068 +-------------------------------------+--------+--------------------+ 1069 | LINKTYPE_FC_2 | 224 |Fibre Channel FC-2 | 1070 | | |frames, beginning | 1071 | | |with a Frame_Header.| 1072 +-------------------------------------+--------+--------------------+ 1073 | LINKTYPE_FC_2_WITH_FRAME_DELIMS | 225 |Fibre Channel FC-2 | 1074 | | |frames, beginning an| 1075 | | |encoding of the SOF,| 1076 | | |followed by a | 1077 | | |Frame_Header, and | 1078 | | |ending with an | 1079 | | |encoding of the SOF.| 1080 | | |The encodings | 1081 | | |represent the frame | 1082 | | |delimiters as 4-byte| 1083 | | |sequences | 1084 | | |representing the | 1085 | | |corresponding | 1086 | | |ordered sets, with | 1087 | | |K28.5 represented as| 1088 | | |0xBC, and the D | 1089 | | |symbols as the | 1090 | | |corresponding byte | 1091 | | |values; for example,| 1092 | | |SOFi2, which is | 1093 | | |K28.5 - D21.5 - D1.2| 1094 | | |- D21.2, is | 1095 | | |represented as 0xBC | 1096 | | |0xB5 0x55 0x55. | 1097 +-------------------------------------+--------+--------------------+ 1098 | LINKTYPE_IPNET | 226 |Solaris ipnet | 1099 | | |pseudo-header , | 1100 | | |followed by an IPv4 | 1101 | | |or IPv6 datagram. | 1102 +-------------------------------------+--------+--------------------+ 1103 | LINKTYPE_CAN_SOCKETCAN | 227 |CAN (Controller Area| 1104 | | |Network) frames, | 1105 | | |with a pseudo-header| 1106 | | |followed by the | 1107 | | |frame payload. | 1108 +-------------------------------------+--------+--------------------+ 1109 | LINKTYPE_IPV4 | 228 |Raw IPv4; the packet| 1110 | | |begins with an IPv4 | 1111 | | |header. | 1112 +-------------------------------------+--------+--------------------+ 1113 | LINKTYPE_IPV6 | 229 |Raw IPv6; the packet| 1114 | | |begins with an IPv6 | 1115 | | |header. | 1116 +-------------------------------------+--------+--------------------+ 1117 | LINKTYPE_IEEE802_15_4_NOFCS | 230 |IEEE 802.15.4 Low- | 1118 | | |Rate Wireless | 1119 | | |Network, without the| 1120 | | |FCS at the end of | 1121 | | |the frame. | 1122 +-------------------------------------+--------+--------------------+ 1123 | LINKTYPE_DBUS | 231 |Raw D-Bus messages ,| 1124 | | |starting with the | 1125 | | |endianness flag, | 1126 | | |followed by the | 1127 | | |message type, etc., | 1128 | | |but without the | 1129 | | |authentication | 1130 | | |handshake before the| 1131 | | |message sequence. | 1132 +-------------------------------------+--------+--------------------+ 1133 | LINKTYPE_JUNIPER_VS | 232 |Reserved for Juniper| 1134 | | |Networks | 1135 +-------------------------------------+--------+--------------------+ 1136 | LINKTYPE_JUNIPER_SRX_E2E | 233 |Reserved for Juniper| 1137 | | |Networks | 1138 +-------------------------------------+--------+--------------------+ 1139 | LINKTYPE_JUNIPER_FIBRECHANNEL | 234 |Reserved for Juniper| 1140 | | |Networks | 1141 +-------------------------------------+--------+--------------------+ 1142 | LINKTYPE_DVB_CI | 235 |DVB-CI (DVB Common | 1143 | | |Interface for | 1144 | | |communication | 1145 | | |between a PC Card | 1146 | | |module and a DVB | 1147 | | |receiver), with the | 1148 | | |message format | 1149 | | |specified by the | 1150 | | |PCAP format for DVB-| 1151 | | |CI specification | 1152 +-------------------------------------+--------+--------------------+ 1153 | LINKTYPE_MUX27010 | 236 |Variant of 3GPP TS | 1154 | | |27.010 multiplexing | 1155 | | |protocol (similar | 1156 | | |to, but not the same| 1157 | | |as, 27.010). | 1158 +-------------------------------------+--------+--------------------+ 1159 | LINKTYPE_STANAG_5066_D_PDU | 237 |D_PDUs as described | 1160 | | |by NATO standard | 1161 | | |STANAG 5066, | 1162 | | |starting with the | 1163 | | |synchronization | 1164 | | |sequence, and | 1165 | | |including both | 1166 | | |header and data | 1167 | | |CRCs. The current | 1168 | | |version of STANAG | 1169 | | |5066 is backwards- | 1170 | | |compatible with the | 1171 | | |1.0.2 version , | 1172 | | |although newer | 1173 | | |versions are | 1174 | | |classified. | 1175 +-------------------------------------+--------+--------------------+ 1176 | LINKTYPE_JUNIPER_ATM_CEMIC | 238 |Reserved for Juniper| 1177 | | |Networks | 1178 +-------------------------------------+--------+--------------------+ 1179 | LINKTYPE_NFLOG | 239 |Linux netlink | 1180 | | |NETLINK NFLOG socket| 1181 | | |log messages. | 1182 +-------------------------------------+--------+--------------------+ 1183 | LINKTYPE_NETANALYZER | 240 |Pseudo-header for | 1184 | | |Hilscher | 1185 | | |Gesellschaft fuer | 1186 | | |Systemautomation mbH| 1187 | | |netANALYZER devices | 1188 | | |, followed by an | 1189 | | |Ethernet frame, | 1190 | | |beginning with the | 1191 | | |MAC header and | 1192 | | |ending with the FCS.| 1193 +-------------------------------------+--------+--------------------+ 1194 | LINKTYPE_NETANALYZER_TRANSPARENT | 241 |Pseudo-header for | 1195 | | |Hilscher | 1196 | | |Gesellschaft fuer | 1197 | | |Systemautomation mbH| 1198 | | |netANALYZER devices | 1199 | | |, followed by an | 1200 | | |Ethernet frame, | 1201 | | |beginning with the | 1202 | | |preamble, SFD, and | 1203 | | |MAC header, and | 1204 | | |ending with the FCS.| 1205 +-------------------------------------+--------+--------------------+ 1206 | LINKTYPE_IPOIB | 242 |IP-over-InfiniBand, | 1207 | | |as specified by RFC | 1208 | | |4391 section 6 | 1209 +-------------------------------------+--------+--------------------+ 1210 | LINKTYPE_MPEG_2_TS | 243 |MPEG-2 Transport | 1211 | | |Stream transport | 1212 | | |packets, as | 1213 | | |specified by ISO | 1214 | | |13818-1/ ITU-T | 1215 | | |Recommendation | 1216 | | |H.222.0 (see table | 1217 | | |2-2 of section | 1218 | | |2.4.3.2 Transport | 1219 | | |Stream packet | 1220 | | |layer). | 1221 +-------------------------------------+--------+--------------------+ 1222 | LINKTYPE_NG40 | 244 |Pseudo-header for | 1223 | | |ng4T GmbH's UMTS | 1224 | | |Iub/Iur-over-ATM and| 1225 | | |Iub/Iur-over-IP | 1226 | | |format as used by | 1227 | | |their ng40 protocol | 1228 | | |tester , followed by| 1229 | | |frames for the Frame| 1230 | | |Protocol as | 1231 | | |specified by 3GPP TS| 1232 | | |25.427 for dedicated| 1233 | | |channels and 3GPP TS| 1234 | | |25.435 for common/ | 1235 | | |shared channels in | 1236 | | |the case of ATM AAL2| 1237 | | |or UDP traffic, by | 1238 | | |SSCOP packets as | 1239 | | |specified by ITU-T | 1240 | | |Recommendation | 1241 | | |Q.2110 for ATM AAL5 | 1242 | | |traffic, and by NBAP| 1243 | | |packets for SCTP | 1244 | | |traffic. | 1245 +-------------------------------------+--------+--------------------+ 1246 | LINKTYPE_NFC_LLCP | 245 |Pseudo-header for | 1247 | | |NFC LLCP packet | 1248 | | |captures , followed | 1249 | | |by frame data for | 1250 | | |the LLCP Protocol as| 1251 | | |specified by | 1252 | | |NFCForum-TS-LLCP_1.1| 1253 +-------------------------------------+--------+--------------------+ 1254 | LINKTYPE_PFSYNC | 246 |Reserved for pfsync | 1255 | | |output | 1256 +-------------------------------------+--------+--------------------+ 1257 | LINKTYPE_INFINIBAND | 247 |Raw InfiniBand | 1258 | | |frames, starting | 1259 | | |with the Local | 1260 | | |Routing Header, as | 1261 | | |specified in Chapter| 1262 | | |5 Data packet format| 1263 | | |of InfiniBand[TM] | 1264 | | |Architectural | 1265 | | |Specification | 1266 | | |Release 1.2.1 Volume| 1267 | | |1 - General | 1268 | | |Specifications | 1269 +-------------------------------------+--------+--------------------+ 1270 | LINKTYPE_SCTP | 248 |SCTP packets, as | 1271 | | |defined by RFC 4960 | 1272 | | |, with no lower- | 1273 | | |level protocols such| 1274 | | |as IPv4 or IPv6. | 1275 +-------------------------------------+--------+--------------------+ 1276 | LINKTYPE_USBPCAP | 249 |USB packets, | 1277 | | |beginning with a | 1278 | | |USBPcap header | 1279 +-------------------------------------+--------+--------------------+ 1280 | LINKTYPE_RTAC_SERIAL | 250 |Serial-line packet | 1281 | | |header for the | 1282 | | |Schweitzer | 1283 | | |Engineering | 1284 | | |Laboratories RTAC | 1285 | | |product , followed | 1286 | | |by a payload for one| 1287 | | |of a number of | 1288 | | |industrial control | 1289 | | |protocols. | 1290 +-------------------------------------+--------+--------------------+ 1291 | LINKTYPE_BLUETOOTH_LE_LL | 251 |Bluetooth Low Energy| 1292 | | |air interface Link | 1293 | | |Layer packets, in | 1294 | | |the format described| 1295 | | |in section 2.1 | 1296 | | |PACKET FORMAT of | 1297 | | |volume 6 of the | 1298 | | |Bluetooth | 1299 | | |Specification | 1300 | | |Version 4.0 (see PDF| 1301 | | |page 2200), but | 1302 | | |without the | 1303 | | |Preamble. | 1304 +-------------------------------------+--------+--------------------+ 1305 | LINKTYPE_WIRESHARK_UPPER_PDU | 252 |Reserved for | 1306 | | |Wireshark | 1307 +-------------------------------------+--------+--------------------+ 1308 | LINKTYPE_NETLINK | 253 |Linux Netlink | 1309 | | |capture | 1310 | | |encapsulation | 1311 +-------------------------------------+--------+--------------------+ 1312 | LINKTYPE_BLUETOOTH_LINUX_MONITOR | 254 |Bluetooth Linux | 1313 | | |Monitor | 1314 | | |encapsulation of | 1315 | | |traffic for the | 1316 | | |BlueZ stack | 1317 +-------------------------------------+--------+--------------------+ 1318 | LINKTYPE_BLUETOOTH_BREDR_BB | 255 |Bluetooth Basic Rate| 1319 | | |and Enhanced Data | 1320 | | |Rate baseband | 1321 | | |packets | 1322 +-------------------------------------+--------+--------------------+ 1323 | LINKTYPE_BLUETOOTH_LE_LL_WITH_PHDR | 256 |Bluetooth Low Energy| 1324 | | |link-layer packets | 1325 +-------------------------------------+--------+--------------------+ 1326 | LINKTYPE_PROFIBUS_DL | 257 |PROFIBUS data link | 1327 | | |layer packets, as | 1328 | | |specified by IEC | 1329 | | |standard 61158-4-3, | 1330 | | |beginning with the | 1331 | | |start delimiter, | 1332 | | |ending with the end | 1333 | | |delimiter, and | 1334 | | |including all octets| 1335 | | |between them. | 1336 +-------------------------------------+--------+--------------------+ 1337 | LINKTYPE_PKTAP | 258 |Apple PKTAP capture | 1338 | | |encapsulation | 1339 +-------------------------------------+--------+--------------------+ 1340 | LINKTYPE_EPON | 259 |Ethernet-over- | 1341 | | |passive-optical- | 1342 | | |network packets, | 1343 | | |starting with the | 1344 | | |last 6 octets of the| 1345 | | |modified preamble as| 1346 | | |specified by | 1347 | | |65.1.3.2 Transmit in| 1348 | | |Clause 65 of | 1349 | | |Section 5 of IEEE | 1350 | | |802.3 , followed | 1351 | | |immediately by an | 1352 | | |Ethernet frame. | 1353 +-------------------------------------+--------+--------------------+ 1354 | LINKTYPE_IPMI_HPM_2 | 260 |IPMI trace packets, | 1355 | | |as specified by | 1356 | | |Table 3-20 Trace | 1357 | | |Data Block Format in| 1358 | | |the PICMG HPM.2 | 1359 | | |specification The | 1360 | | |time stamps for | 1361 | | |packets in this | 1362 | | |format must match | 1363 | | |the time stamps in | 1364 | | |the Trace Data | 1365 | | |Blocks. | 1366 +-------------------------------------+--------+--------------------+ 1367 | LINKTYPE_ZWAVE_R1_R2 | 261 |Z-Wave RF profile R1| 1368 | | |and R2 packets , as | 1369 | | |specified by ITU-T | 1370 | | |Recommendation | 1371 | | |G.9959 , with some | 1372 | | |MAC layer fields | 1373 | | |moved. | 1374 +-------------------------------------+--------+--------------------+ 1375 | LINKTYPE_ZWAVE_R3 | 262 |Z-Wave RF profile R3| 1376 | | |packets , as | 1377 | | |specified by ITU-T | 1378 | | |Recommendation | 1379 | | |G.9959 , with some | 1380 | | |MAC layer fields | 1381 | | |moved. | 1382 +-------------------------------------+--------+--------------------+ 1383 | LINKTYPE_WATTSTOPPER_DLM | 263 |Formats for | 1384 | | |WattStopper Digital | 1385 | | |Lighting Management | 1386 | | |(DLM) and Legrand | 1387 | | |Nitoo Open protocol | 1388 | | |common packet | 1389 | | |structure captures. | 1390 +-------------------------------------+--------+--------------------+ 1391 | LINKTYPE_ISO_14443 | 264 |Messages between ISO| 1392 | | |14443 contactless | 1393 | | |smartcards | 1394 | | |(Proximity | 1395 | | |Integrated Circuit | 1396 | | |Card, PICC) and card| 1397 | | |readers (Proximity | 1398 | | |Coupling Device, | 1399 | | |PCD), with the | 1400 | | |message format | 1401 | | |specified by the | 1402 | | |PCAP format for | 1403 | | |ISO14443 | 1404 | | |specification | 1405 +-------------------------------------+--------+--------------------+ 1406 | LINKTYPE_RDS | 265 |Radio data system | 1407 | | |(RDS) groups, as per| 1408 | | |IEC 62106, | 1409 | | |encapsulated in this| 1410 | | |form | 1411 +-------------------------------------+--------+--------------------+ 1412 | LINKTYPE_USB_DARWIN | 266 |USB packets, | 1413 | | |beginning with a | 1414 | | |Darwin (macOS, etc.)| 1415 | | |USB header | 1416 +-------------------------------------+--------+--------------------+ 1417 | LINKTYPE_OPENFLOW | 267 |Reserved for OpenBSD| 1418 | | |DLT_OPENFLOW | 1419 +-------------------------------------+--------+--------------------+ 1420 | LINKTYPE_SDLC | 268 |SDLC packets, as | 1421 | | |specified by Chapter| 1422 | | |1, DLC Links, | 1423 | | |section Synchronous | 1424 | | |Data Link Control | 1425 | | |(SDLC) of Systems | 1426 | | |Network Architecture| 1427 | | |Formats, | 1428 | | |GA27-3136-20 , | 1429 | | |without the flag | 1430 | | |fields, zero-bit | 1431 | | |insertion, or Frame | 1432 | | |Check Sequence | 1433 | | |field, containing | 1434 | | |SNA path information| 1435 | | |units (PIUs) as the | 1436 | | |payload. | 1437 +-------------------------------------+--------+--------------------+ 1438 | LINKTYPE_TI_LLN_SNIFFER | 269 |Reserved for Texas | 1439 | | |Instruments protocol| 1440 | | |sniffer | 1441 +-------------------------------------+--------+--------------------+ 1442 | LINKTYPE_LORATAP | 270 |LoRaTap pseudo- | 1443 | | |header , followed by| 1444 | | |the payload, which | 1445 | | |is typically the | 1446 | | |PHYPayload from the | 1447 | | |LoRaWan | 1448 | | |specification | 1449 +-------------------------------------+--------+--------------------+ 1450 | LINKTYPE_VSOCK | 271 |Protocol for | 1451 | | |communication | 1452 | | |between host and | 1453 | | |guest machines in | 1454 | | |VMware and KVM | 1455 | | |hypervisors. | 1456 +-------------------------------------+--------+--------------------+ 1457 | LINKTYPE_NORDIC_BLE | 272 |Messages to and from| 1458 | | |a Nordic | 1459 | | |Semiconductor nRF | 1460 | | |Sniffer for | 1461 | | |Bluetooth LE | 1462 | | |packets, beginning | 1463 | | |with a pseudo-header| 1464 +-------------------------------------+--------+--------------------+ 1465 | LINKTYPE_DOCSIS31_XRA31 | 273 |DOCSIS packets and | 1466 | | |bursts, preceded by | 1467 | | |a pseudo-header | 1468 | | |giving metadata | 1469 | | |about the packet | 1470 +-------------------------------------+--------+--------------------+ 1471 | LINKTYPE_ETHERNET_MPACKET | 274 |mPackets, as | 1472 | | |specified by IEEE | 1473 | | |802.3br Figure 99-4,| 1474 | | |starting with the | 1475 | | |preamble and always | 1476 | | |ending with a CRC | 1477 | | |field. | 1478 +-------------------------------------+--------+--------------------+ 1479 | LINKTYPE_DISPLAYPORT_AUX | 275 |DisplayPort AUX | 1480 | | |channel monitoring | 1481 | | |data as specified by| 1482 | | |VESA DisplayPort(DP)| 1483 | | |Standard preceded by| 1484 | | |a pseudo-header | 1485 +-------------------------------------+--------+--------------------+ 1486 | LINKTYPE_LINUX_SLL2 | 276 |Linux cooked capture| 1487 | | |encapsulation v2 | 1488 +-------------------------------------+--------+--------------------+ 1489 | LINKTYPE_SERCOS_MONITOR | 277 |Reserved for Sercos | 1490 | | |Monitor | 1491 +-------------------------------------+--------+--------------------+ 1492 | LINKTYPE_OPENVIZSLA | 278 |Openvizsla FPGA- | 1493 | | |based USB sniffer | 1494 +-------------------------------------+--------+--------------------+ 1495 | LINKTYPE_EBHSCR | 279 |Elektrobit High | 1496 | | |Speed Capture and | 1497 | | |Replay (EBHSCR) | 1498 | | |format | 1499 +-------------------------------------+--------+--------------------+ 1500 | LINKTYPE_VPP_DISPATCH | 280 |Records in traces | 1501 | | |from the | 1502 | | |http://fd.io VPP | 1503 | | |graph dispatch | 1504 | | |tracer, in the the | 1505 | | |graph dispatcher | 1506 | | |trace format | 1507 +-------------------------------------+--------+--------------------+ 1508 | LINKTYPE_DSA_TAG_BRCM | 281 |Ethernet frames, | 1509 | | |with a switch tag | 1510 | | |inserted between the| 1511 | | |source address field| 1512 | | |and the type/length | 1513 | | |field in the | 1514 | | |Ethernet header. | 1515 +-------------------------------------+--------+--------------------+ 1516 | LINKTYPE_DSA_TAG_BRCM_PREPEND | 282 |Ethernet frames, | 1517 | | |with a switch tag | 1518 | | |inserted before the | 1519 | | |destination address | 1520 | | |in the Ethernet | 1521 | | |header. | 1522 +-------------------------------------+--------+--------------------+ 1523 | LINKTYPE_IEEE802_15_4_TAP | 283 |IEEE 802.15.4 Low- | 1524 | | |Rate Wireless | 1525 | | |Networks, with a | 1526 | | |pseudo-header | 1527 | | |containing TLVs with| 1528 | | |metadata preceding | 1529 | | |the 802.15.4 header.| 1530 +-------------------------------------+--------+--------------------+ 1531 | LINKTYPE_DSA_TAG_DSA | 284 |Ethernet frames, | 1532 | | |with a switch tag | 1533 | | |inserted between the| 1534 | | |source address field| 1535 | | |and the type/length | 1536 | | |field in the | 1537 | | |Ethernet header. | 1538 +-------------------------------------+--------+--------------------+ 1539 | LINKTYPE_DSA_TAG_EDSA | 285 |Ethernet frames, | 1540 | | |with a programmable | 1541 | | |Ethernet type switch| 1542 | | |tag inserted between| 1543 | | |the source address | 1544 | | |field and the type/ | 1545 | | |length field in the | 1546 | | |Ethernet header. | 1547 +-------------------------------------+--------+--------------------+ 1548 | LINKTYPE_ELEE | 286 |Payload of lawful | 1549 | | |intercept packets | 1550 | | |using the ELEE | 1551 | | |protocol The packet | 1552 | | |begins with the ELEE| 1553 | | |header; it does not | 1554 | | |include any | 1555 | | |transport-layer or | 1556 | | |lower-layer headers | 1557 | | |for protcols used to| 1558 | | |transport ELEE | 1559 | | |packets. | 1560 +-------------------------------------+--------+--------------------+ 1561 | LINKTYPE_Z_WAVE_SERIAL | 287 |Serial frames | 1562 | | |transmitted between | 1563 | | |a host and a Z-Wave | 1564 | | |chip over an RS-232 | 1565 | | |or USB serial | 1566 | | |connection, as | 1567 | | |described in section| 1568 | | |5 of the Z-Wave | 1569 | | |Serial API Host | 1570 | | |Application | 1571 | | |Programming Guide | 1572 +-------------------------------------+--------+--------------------+ 1573 | LINKTYPE_USB_2_0 | 288 |USB 2.0, 1.1, or 1.0| 1574 | | |packet, beginning | 1575 | | |with a PID, as | 1576 | | |described by Chapter| 1577 | | |8 Protocol Layer of | 1578 | | |the the Universal | 1579 | | |Serial Bus | 1580 | | |Specification | 1581 | | |Revision 2.0 | 1582 +-------------------------------------+--------+--------------------+ 1583 | LINKTYPE_ATSC_ALP | 289 |ATSC Link-Layer | 1584 | | |Protocol frames, as | 1585 | | |described in section| 1586 | | |5 of the A/330 Link-| 1587 | | |Layer Protocol | 1588 | | |specification, found| 1589 | | |at the ATSC 3.0 | 1590 | | |standards page , | 1591 | | |beginning with a | 1592 | | |Base Header | 1593 +-------------------------------------+--------+--------------------+ 1595 Table 1 1597 9. Contributors 1599 [Insert pcap developers etc. here]. 1601 10. Acknowledgments 1603 The authors wish to thank [insert list here] and many others for 1604 their invaluable comments. 1606 11. References 1608 11.1. Normative References 1610 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1611 Requirement Levels", BCP 14, RFC 2119, 1612 DOI 10.17487/RFC2119, March 1997, 1613 . 1615 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1616 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1617 May 2017, . 1619 11.2. Informative References 1621 [I-D.tuexen-opsawg-pcapng] 1622 Tuexen, M., Risso, F., Bongertz, J., Combs, G., Harris, 1623 G., Chaudron, E., and M. C. Richardson, "PCAP Next 1624 Generation (pcapng) Capture File Format", Work in 1625 Progress, Internet-Draft, draft-tuexen-opsawg-pcapng-04, 4 1626 October 2021, . 1629 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 1630 Writing an IANA Considerations Section in RFCs", BCP 26, 1631 RFC 8126, DOI 10.17487/RFC8126, June 2017, 1632 . 1634 [Radiotap] radiotap.org, "Radiotap Web site", n.d., 1635 . 1637 [AVS] Peachy, S., "Archived AVS specification", n.d., 1638 . 1641 Authors' Addresses 1643 Guy Harris (editor) 1645 Email: gharris@sonic.net 1646 Michael C. Richardson 1647 Sandelman Software Works Inc 1649 Email: mcr+ietf@sandelman.ca 1650 URI: http://www.sandelman.ca/