-
Notifications
You must be signed in to change notification settings - Fork 62
/
linktypes.csv
We can make this file beautiful and searchable if this error is corrected: Illegal quoting in line 30.
218 lines (218 loc) · 23.2 KB
/
linktypes.csv
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
|LINKTYPE_NULL|0|BSD loopback encapsulation|{{LINKTYPE_NULL}}
|LINKTYPE_ETHERNET|1|IEEE 802.3 Ethernet|
|LINKTYPE_EXP_ETHERNET|2|Xerox experimental 3Mb Ethernet|{{PracConsEthDesign}}
|LINKTYPE_AX25|3|AX.25 layer 2 packets|{{AX.25}}
|LINKTYPE_PRONET|4|Reserved for Proteon PRONet Token Ring|
|LINKTYPE_CHAOS|5|Reserved for MIT Chaosnet|{{AIM-628}}
|LINKTYPE_IEEE802_5|6|IEEE 802.5 Token Ring|
|LINKTYPE_ARCNET_BSD|7|Reserved for ARCNET Data Packets with BSD encapsulation|{{ATA-878.1-1999}}{{Draft-ATA-878.2}}{{?RFC1051}}{{?RFC1201}}
|LINKTYPE_SLIP|8|SLIP|{{LINKTYPE_SLIP}}
|LINKTYPE_PPP|9|PPP|{{?RFC1661}}/{{?RFC1662}}
|LINKTYPE_FDDI|10|FDDI: per ANSI INCITS 239-1994|
|not to be used|11-49|Do not use these values|
|LINKTYPE_PPP_HDLC|50|PPP in HDLC-like framing|{{?RFC1662}}
|LINKTYPE_PPP_ETHER|51|PPPoE|{{Section 4 of ?RFC2516}}
|Reserved|52-98|Do not use these values|
|LINKTYPE_SYMANTEC_FIREWALL|99|Reserved for Symantec Enterprise Firewall|
|LINKTYPE_ATM_RFC1483|100|LLC/SNAP-encapsulated ATM|{{?RFC1483}}
|LINKTYPE_RAW|101|Raw IP; begins with an IPv4 or IPv6 header|
|LINKTYPE_SLIP_BSDOS|102|Reserved for BSD/OS SLIP BPF header|
|LINKTYPE_PPP_BSDOS|103|Reserved for BSD/OS PPP BPF header|
|LINKTYPE_C_HDLC|104|Cisco PPP with HDLC framing|{{Section 4.3.1 of ?RFC1547}}
|LINKTYPE_IEEE802_11|105|IEEE 802.11 wireless LAN|
|LINKTYPE_ATM_CLIP|106|ATM Classical IP, with no header preceding IP|
|LINKTYPE_FRELAY|107|Frame Relay LAPF frames|
|LINKTYPE_LOOP|108|OpenBSD loopback encapsulation|{{LINKTYPE_LOOP}}
|LINKTYPE_ENC|109|Reserved for OpenBSD IPSEC encapsulation|
|LINKTYPE_LANE8023|110|Reserved for ATM LANE + 802.3|
|LINKTYPE_HIPPI|111|Reserved for NetBSD HIPPI|
|LINKTYPE_HDLC|112|Reserved for NetBSD HDLC framing|
|LINKTYPE_LINUX_SLL|113|"Linux ""cooked"" capture encapsulation"|{{LINKTYPE_LINUX_SLL}}
|LINKTYPE_LTALK|114|Apple LocalTalk|
|LINKTYPE_ECONET|115|Reserved for Acorn Econet|
|LINKTYPE_IPFILTER|116|Reserved for OpenBSD ipfilter|
|LINKTYPE_PFLOG|117|"OpenBSD pflog; ""struct pfloghdr"" structure"|
|LINKTYPE_CISCO_IOS|118|Reserved for Cisco-internal use|
|LINKTYPE_IEEE802_11_PRISM|119|Prism monitor mode|{{LINKTYPE_IEEE802_11_PRISM}}
|LINKTYPE_IEEE802_11_AIRONET|120|Reserved for 802.11 + FreeFreeBSD Aironet radio metadata|
|LINKTYPE_HHDLC|121|Reserved for Siemens HiPath HDLC|
|LINKTYPE_IP_OVER_FC|122|IP-over-Fibre Channel, starting with the Network_Header|{{?RFC2625}}
|LINKTYPE_SUNATM|123|ATM traffic captured from a SunATM device|{{LINKTYPE_SUNATM}}
|LINKTYPE_RIO|124|Reserved for RapidIO|
|LINKTYPE_PCI_EXP|125|Reserved for PCI Express|
|LINKTYPE_AURORA|126|Reserved for Xilinx Aurora link layer|
|LINKTYPE_IEEE802_11_RADIOTAP|127|Radiotap header, followed by an 802.11 header|{{Radiotap}}
|LINKTYPE_TZSP|128|Reserved for Tazmen Sniffer Protocol|
|LINKTYPE_ARCNET_LINUX|129|Reserved for ARCNET Data Packets with Linux encapsulation|{{ATA-878.1-1999}}{{Draft-ATA-878.2}}{{?RFC1051}}{{?RFC1201}}
|LINKTYPE_JUNIPER_MLPPP|130|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_MLFR|131|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_ES|132|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_GGSN|133|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_MFR|134|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_ATM2|135|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_SERVICES|136|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_ATM1|137|Reserved for Juniper Networks|
|LINKTYPE_APPLE_IP_OVER_IEEE1394|138|Apple IP-over-IEEE 1394 cooked header|{{LINKTYPE_APPLE_IP_OVER_IEEE1394}}
|LINKTYPE_MTP2_WITH_PHDR|139|Signaling System 7 (SS7) Message Transfer Part Level|{{Q.703}}
|LINKTYPE_MTP2|140|SS7 Level 2|{{Q.703}}
|LINKTYPE_MTP3|141|SS7 Level 3, with no MTP2 header|{{Q.704}}
|LINKTYPE_SCCP|142|SS7 Control Part, with no MTP3 or MTP2 header|{{Q.711}} {{Q.712}} {{Q.713}} {{Q.714}}
|LINKTYPE_DOCSIS|143|DOCSIS MAC frames|{{DOCSIS-4.0-MULP}}
|LINKTYPE_LINUX_IRDA|144|Linux-IrDA packets|{{LINKTYPE_LINUX_IRDA}}
|LINKTYPE_IBM_SP|145|Reserved for IBM SP switch|
|LINKTYPE_IBM_SN|146|Reserved for IBM Next Federation switch|
|LINKTYPE_RESERVED_01|147|For private use (deprecated)|
|LINKTYPE_RESERVED_02|148|For private use (deprecated)|
|LINKTYPE_RESERVED_03|149|For private use (deprecated)|
|LINKTYPE_RESERVED_04|150|For private use (deprecated)|
|LINKTYPE_RESERVED_05|151|For private use (deprecated)|
|LINKTYPE_RESERVED_06|152|For private use (deprecated)|
|LINKTYPE_RESERVED_07|153|For private use (deprecated)|
|LINKTYPE_RESERVED_08|154|For private use (deprecated)|
|LINKTYPE_RESERVED_09|155|For private use (deprecated)|
|LINKTYPE_RESERVED_10|156|For private use (deprecated)|
|LINKTYPE_RESERVED_11|157|For private use (deprecated)|
|LINKTYPE_RESERVED_12|158|For private use (deprecated)|
|LINKTYPE_RESERVED_13|159|For private use (deprecated)|
|LINKTYPE_RESERVED_14|160|For private use (deprecated)|
|LINKTYPE_RESERVED_15|161|For private use (deprecated)|
|LINKTYPE_RESERVED_16|162|For private use (deprecated)|
|LINKTYPE_IEEE802_11_AVS|163|AVS header, followed by an 802.11 header|{{AVS}}
|LINKTYPE_JUNIPER_MONITOR|164|Reserved for Juniper Networks|
|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_JUNIPER_PPPOE|167|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_PPPOE_ATM|168|Reserved for Juniper Networks|
|LINKTYPE_GPRS_LLC|169|General Packet Radio Service Logical Link Control, as per 3GPP TS 04.64|{{_3GPP-TS-04.64}}
|LINKTYPE_GPF_T|170|Transparent-mapped generic framing procedure|{{G.7041}}
|LINKTYPE_GPF_F|171|Frame-mapped generic framing procedure|{{G.7041}}
|LINKTYPE_GCOM_T1E1|172|Reserved for Gcom T1/E1 line monitoring equipment|
|LINKTYPE_GCOM_SERIAL|173|Reserved for Gcom T1/E1 line monitoring equipment|
|LINKTYPE_JUNIPER_PIC_PEER|174|Reserved for Juniper Networks|
|LINKTYPE_ERF_ETH|175|Endace ERF header followed by 802.3 Ethernet|
|LINKTYPE_ERF_POS|176|Endace ERF header followed by Packet-over-SONET|
|LINKTYPE_LINUX_LAPD|177|Linux vISDN LAPD frames|{{LINKTYPE_LINUX_LAPD}}
|LINKTYPE_JUNIPER_ETHER|178|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_PPP|179|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_FRELAY|180|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_CHDLC|181|Reserved for Juniper Networks|
|LINKTYPE_MFR|182|FRF.16.1 Multi-Link Frame Relay frames, beginning with an FRF.12 Interface fragmentation format fragmentation header|{{FRF.16.1}}
|LINKTYPE_JUNIPER_VP|183|Reserved for Juniper Networks|
|LINKTYPE_A429|184|Reserved for ARINC 429 frames|
|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|{{PPI}}
|LINKTYPE_IEEE802_16_MAC_CPS_RADIO|193|Reserved for 802.16 MAC Common Part Sublayer plus radio header|
|LINKTYPE_JUNIPER_ISM|194|Reserved for Juniper Networks|
|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_SITA}}
|LINKTYPE_ERF|197|Endace ERF records|{{ERF}}
|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_JUNIPER_ST|200|Reserved for Juniper Networks|
|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_AX25_KISS|202|AX.25 packet, with a KISS header|{{KISS}} {{AX.25}}
|LINKTYPE_LAPD|203|Link Access Procedures on the D Channel (LAPD) frames, starting with the address field, with no pseudo-header|{{Q.920}} {{Q.921}}
|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)|
|Reserved|208|Reserved for an unspecified link-layer type|
|LINKTYPE_I2C_LINUX|209|Linux I2C packets|{{LINKTYPE_I2C_LINUX}}
|LINKTYPE_FLEXRAY|210|FlexRay frames or symbols, with a pseudo-header|{{LINKTYPE_FLEXRAY}}
|LINKTYPE_MOST|211|Reserved for Media Oriented Systems Transport (MOST) bus|
|LINKTYPE_LIN|212|Local Interconnect Network (LIN) automotive bus|{{LINKTYPE_LIN}}
|LINKTYPE_X2E_SERIAL|213|Reserved for X2E serial line captures|
|LINKTYPE_X2E_XORAYA|214|Reserved for X2E Xoraya data loggers|
|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_LINUX_EVDEV|216|Reserved for Linux evdev messages|
|LINKTYPE_GSMTAP_UM|217|Reserved for GSM Um interface, with gsmtap header|
|LINKTYPE_GSMTAP_ABIS|218|Reserved for GSM Abis interface, with gsmtap header|
|LINKTYPE_MPLS|219|MPLS packets with MPLS label as the 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_DECT|221|Reserved for DECT packets, with a pseudo-header|
|LINKTYPE_AOS|222|Reserved for OS Space Data Link Protocol|
|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_IPNET|226|Solaris ipnet|{{LINKTYPE_IPNET}}
|LINKTYPE_CAN_SOCKETCAN|227|Controller Area Network frames|{{LINKTYPE_CAN_SOCKETCAN}}
|LINKTYPE_IPV4|228|Raw IPv4; the packet begins with an IPv4 header|
|LINKTYPE_IPV6|229|Raw IPv6; the packet begins with an IPv6 header|
|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|{{D-Bus}}
|LINKTYPE_JUNIPER_VS|232|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_SRX_E2E|233|Reserved for Juniper Networks|
|LINKTYPE_JUNIPER_FIBRECHANNEL|234|Reserved for Juniper Networks|
|LINKTYPE_DVB_CI|235|DVB-CI messages|{{DVB-CI-PCAP}}{{DVB-CI}}
|LINKTYPE_MUX27010|236|Variant of 3GPP TS 27.010 multiplexing protocol|{{LINKTYPE_MUX27010}}
|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|{{STANAG-5066}}
|LINKTYPE_JUNIPER_ATM_CEMIC|238|Reserved for Juniper Networks|
|LINKTYPE_NFLOG|239|Linux netlink NETLINK NFLOG socket log messages|{{LINKTYPE_NFLOG}}
|LINKTYPE_NETANALYZER|240|Ethernet frames with netANALYZER pseudo-header|{{LINKTYPE_NETANALYZER}}
|LINKTYPE_NETANALYZER_TRANSPARENT|241|Ethernet frames with netANALYZER pseudo-header, preamble, and SFD|{{LINKTYPE_NETANALYZER_TRANSPARENT}}
|LINKTYPE_IPOIB|242|IP-over-InfiniBand|{{Section 6 of ?RFC4391}}
|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_NG40|244|Frames from ng4T GmbH's ng40 protocol tester|{{LINKTYPE_NG40}}
|LINKTYPE_NFC_LLCP|245|NFC Logical Link Control Protocol frames, with a pseudo-header|{{LINKTYPE_NFC_LLCP}}
|LINKTYPE_PFSYNC|246|Reserved for pfsync output|
|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|{{USBPcap}}
|LINKTYPE_RTAC_SERIAL|250|Serial-line packet from the Schweitzer Engineering Laboratories RTAC product|{{LINKTYPE_RTAC_SERIAL}}
|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_WIRESHARK_UPPER_PDU|252|Reserved for Wireshark|
|LINKTYPE_NETLINK|253|Linux Netlink capture encapsulation|{{LINKTYPE_NETLINK}} {{?RFC3549}}
|LINKTYPE_BLUETOOTH_LINUX_MONITOR|254|Bluetooth Linux Monitor|{{LINKTYPE_BLUETOOTH_LINUX_MONITOR}}
|LINKTYPE_BLUETOOTH_BREDR_BB|255|Bluetooth Basic Rate and Enhanced Data Rate baseband packets|{{LINKTYPE_BLUETOOTH_BREDR_BB}}
|LINKTYPE_BLUETOOTH_LE_LL_WITH_PHDR|256|Bluetooth Low Energy link-layer packets|{{LINKTYPE_BLUETOOTH_LE_LL_WITH_PHDR}}
|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_PKTAP|258|Apple PKTAP capture encapsulation|{{LINKTYPE_PKTAP}}
|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_ZWAVE_R1_R2|261|Z-Wave RF profile R1 and R2 packets|{{LINKTYPE_ZWAVE_R1_R2}}
|LINKTYPE_ZWAVE_R3|262|Z-Wave RF profile R3 packets|{{LINKTYPE_ZWAVE_R3}}
|LINKTYPE_WATTSTOPPER_DLM|263|WattStopper Digital Lighting Management (DLM) and Legrand Nitoo Open protocol packets|{{LINKTYPE_WATTSTOPPER_DLM}}
|LINKTYPE_ISO_14443|264|ISO 14443 contactless smartcard messages|{{ISO-14443-PCAP}}
|LINKTYPE_RDS|265|IEC 62106 Radio data system (RDS) groups|{{LINKTYPE_RDS}}
|LINKTYPE_USB_DARWIN|266|USB packets captured on a Darwin-based operating system (macOS, etc.)|{{LINKTYPE_USB_DARWIN}}
|LINKTYPE_OPENFLOW|267|Reserved for OpenBSD DLT_OPENFLOW|
|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|{{LoRaTap}}{{LoRaWAN}}
|LINKTYPE_VSOCK|271|Protocol for communication between host and guest machines in VMware and KVM hypervisors|{{LINKTYPE_VSOCK}}
|LINKTYPE_NORDIC_BLE|272|Messages to and from a Nordic Semiconductor nRF Sniffer for Bluetooth LE packets|{{LINKTYPE_NORDIC_BLE}}
|LINKTYPE_DOCSIS31_XRA31|273|DOCSIS packets and bursts, preceded by a pseudo-header|{{DOCSIS-XRA}} {{DOCSIS-4.0-MULP}}
|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_DISPLAYPORT_AUX}}
|LINKTYPE_LINUX_SLL2|276|Linux cooked capture encapsulation v2|{{LINKTYPE_LINUX_SLL2}}
|LINKTYPE_SERCOS_MONITOR|277|Reserved for Sercos Monitor|
|LINKTYPE_OPENVIZSLA|278|OpenVizsla FPGA-based USB sniffer|{{OpenVizsla}}
|LINKTYPE_EBHSCR|279|Elektrobit High Speed Capture and Replay (EBHSCR) format|{{EBHSCR}}
|LINKTYPE_VPP_DISPATCH|280|fd.io VPP graph dispatcher trace records|{{FD.io-VPP}}
|LINKTYPE_DSA_TAG_BRCM|281|Ethernet frames, with a Broadcom switch tag inserted|{{LINKTYPE_DSA_TAG_BRCM}}
|LINKTYPE_DSA_TAG_BRCM_PREPEND|282|Ethernet frames, with a Broadcom switch tag prepended|{{LINKTYPE_DSA_TAG_BRCM_PREPEND}}
|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_DSA}}
|LINKTYPE_DSA_TAG_EDSA|285|Ethernet frames, with a Marvell EDSA switch tag inserted|{{LINKTYPE_DSA_TAG_EDSA}}
|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_ETW|290|Event Tracing for Windows messages|{{LINKTYPE_ETW}}
|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_ZBOSS_NCP}}
|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|{{Exegin-TAP-Link}}{{G.9959}}
|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_FIRA_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|