| 1 | /* $NetBSD: dlt.h,v 1.25 2024/09/02 15:34:08 christos Exp $ */ |
| 2 | |
| 3 | /*- |
| 4 | * Copyright (c) 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997 |
| 5 | * The Regents of the University of California. All rights reserved. |
| 6 | * |
| 7 | * This code is derived from the Stanford/CMU enet packet filter, |
| 8 | * (net/enet.c) distributed as part of 4.3BSD, and code contributed |
| 9 | * to Berkeley by Steven McCanne and Van Jacobson both of Lawrence |
| 10 | * Berkeley Laboratory. |
| 11 | * |
| 12 | * Redistribution and use in source and binary forms, with or without |
| 13 | * modification, are permitted provided that the following conditions |
| 14 | * are met: |
| 15 | * 1. Redistributions of source code must retain the above copyright |
| 16 | * notice, this list of conditions and the following disclaimer. |
| 17 | * 2. Redistributions in binary form must reproduce the above copyright |
| 18 | * notice, this list of conditions and the following disclaimer in the |
| 19 | * documentation and/or other materials provided with the distribution. |
| 20 | * 3. Neither the name of the University nor the names of its contributors |
| 21 | * may be used to endorse or promote products derived from this software |
| 22 | * without specific prior written permission. |
| 23 | * |
| 24 | * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND |
| 25 | * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE |
| 26 | * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE |
| 27 | * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE |
| 28 | * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL |
| 29 | * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS |
| 30 | * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) |
| 31 | * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT |
| 32 | * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY |
| 33 | * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF |
| 34 | * SUCH DAMAGE. |
| 35 | * |
| 36 | * @(#)bpf.h 7.1 (Berkeley) 5/7/91 |
| 37 | */ |
| 38 | |
| 39 | #ifndef _NET_DLT_H_ |
| 40 | #define _NET_DLT_H_ |
| 41 | |
| 42 | /* |
| 43 | * Link-layer header type codes. |
| 44 | * |
| 45 | * Do *NOT* add new values to this list without asking |
| 46 | * "tcpdump-workers@lists.tcpdump.org" for a value. Otherwise, you run |
| 47 | * the risk of using a value that's already being used for some other |
| 48 | * purpose, and of having tools that read libpcap-format captures not |
| 49 | * being able to handle captures with your new DLT_ value, with no hope |
| 50 | * that they will ever be changed to do so (as that would destroy their |
| 51 | * ability to read captures using that value for that other purpose). |
| 52 | * |
| 53 | * See |
| 54 | * |
| 55 | * https://www.tcpdump.org/linktypes.html |
| 56 | * |
| 57 | * for detailed descriptions of some of these link-layer header types. |
| 58 | */ |
| 59 | |
| 60 | /* |
| 61 | * These are the types that are the same on all platforms, and that |
| 62 | * have been defined by <net/bpf.h> for ages. |
| 63 | * |
| 64 | * DLT_LOW_MATCHING_MIN is the lowest such value; DLT_LOW_MATCHING_MAX |
| 65 | * is the highest such value. |
| 66 | */ |
| 67 | #define DLT_LOW_MATCHING_MIN 0 |
| 68 | |
| 69 | #define DLT_NULL 0 /* BSD loopback encapsulation */ |
| 70 | #define DLT_EN10MB 1 /* Ethernet (10Mb) */ |
| 71 | #define DLT_EN3MB 2 /* Experimental Ethernet (3Mb) */ |
| 72 | #define DLT_AX25 3 /* Amateur Radio AX.25 */ |
| 73 | #define DLT_PRONET 4 /* Proteon ProNET Token Ring */ |
| 74 | #define DLT_CHAOS 5 /* Chaos */ |
| 75 | #define DLT_IEEE802 6 /* 802.5 Token Ring */ |
| 76 | #define DLT_ARCNET 7 /* ARCNET, with BSD-style header */ |
| 77 | #define DLT_SLIP 8 /* Serial Line IP */ |
| 78 | #define DLT_PPP 9 /* Point-to-point Protocol */ |
| 79 | #define DLT_FDDI 10 /* FDDI */ |
| 80 | |
| 81 | /* |
| 82 | * In case the code that includes this file (directly or indirectly) |
| 83 | * has also included OS files that happen to define DLT_LOW_MATCHING_MAX, |
| 84 | * with a different value (perhaps because that OS hasn't picked up |
| 85 | * the latest version of our DLT definitions), we undefine the |
| 86 | * previous value of DLT_LOW_MATCHING_MAX. |
| 87 | * |
| 88 | * (They shouldn't, because only those 10 values were assigned in |
| 89 | * the Good Old Days, before DLT_ code assignment became a bit of |
| 90 | * a free-for-all. Perhaps 11 is DLT_ATM_RFC1483 everywhere 11 |
| 91 | * is used at all, but 12 is DLT_RAW on some platforms but not |
| 92 | * OpenBSD, and the fun continues for several other values.) |
| 93 | */ |
| 94 | #ifdef DLT_LOW_MATCHING_MAX |
| 95 | #undef DLT_LOW_MATCHING_MAX |
| 96 | #endif |
| 97 | |
| 98 | #define DLT_LOW_MATCHING_MAX DLT_FDDI /* highest value in this "matching" range */ |
| 99 | |
| 100 | /* |
| 101 | * These are types that are different on some platforms, and that |
| 102 | * have been defined by <net/bpf.h> for ages. We use #ifdefs to |
| 103 | * detect the BSDs that define them differently from the traditional |
| 104 | * libpcap <net/bpf.h> |
| 105 | * |
| 106 | * XXX - DLT_ATM_RFC1483 is 13 in BSD/OS, and DLT_RAW is 14 in BSD/OS, |
| 107 | * but I don't know what the right #define is for BSD/OS. The last |
| 108 | * release was in October 2003; if anybody cares about making this |
| 109 | * work on BSD/OS, give us a pull request for a change to make it work. |
| 110 | */ |
| 111 | #define DLT_ATM_RFC1483 11 /* LLC-encapsulated ATM */ |
| 112 | |
| 113 | #ifdef __OpenBSD__ |
| 114 | #define DLT_RAW 14 /* raw IP */ |
| 115 | #else |
| 116 | #define DLT_RAW 12 /* raw IP */ |
| 117 | #endif |
| 118 | |
| 119 | /* |
| 120 | * Given that the only OS that currently generates BSD/OS SLIP or PPP |
| 121 | * is, well, BSD/OS, arguably everybody should have chosen its values |
| 122 | * for DLT_SLIP_BSDOS and DLT_PPP_BSDOS, which are 15 and 16, but they |
| 123 | * didn't. So it goes. |
| 124 | */ |
| 125 | #if defined(__NetBSD__) || defined(__FreeBSD__) |
| 126 | #ifndef DLT_SLIP_BSDOS |
| 127 | #define DLT_SLIP_BSDOS 13 /* BSD/OS Serial Line IP */ |
| 128 | #define DLT_PPP_BSDOS 14 /* BSD/OS Point-to-point Protocol */ |
| 129 | #endif |
| 130 | #else |
| 131 | #define DLT_SLIP_BSDOS 15 /* BSD/OS Serial Line IP */ |
| 132 | #define DLT_PPP_BSDOS 16 /* BSD/OS Point-to-point Protocol */ |
| 133 | #endif |
| 134 | |
| 135 | /* |
| 136 | * NetBSD uses 15 for HIPPI. |
| 137 | * |
| 138 | * From a quick look at sys/net/if_hippi.h and sys/net/if_hippisubr.c |
| 139 | * in an older version of NetBSD , the header appears to be: |
| 140 | * |
| 141 | * a 1-byte ULP field (ULP-id)? |
| 142 | * |
| 143 | * a 1-byte flags field; |
| 144 | * |
| 145 | * a 2-byte "offsets" field; |
| 146 | * |
| 147 | * a 4-byte "D2 length" field (D2_Size?); |
| 148 | * |
| 149 | * a 4-byte "destination switch" field (or a 1-byte field |
| 150 | * containing the Forwarding Class, Double_Wide, and Message_Type |
| 151 | * sub fields, followed by a 3-byte Destination_Switch_Address |
| 152 | * field?, HIPPI-LE 3.4-style?); |
| 153 | * |
| 154 | * a 4-byte "source switch" field (or a 1-byte field containing the |
| 155 | * Destination_Address_type and Source_Address_Type fields, followed |
| 156 | * by a 3-byte Source_Switch_Address field, HIPPI-LE 3.4-style?); |
| 157 | * |
| 158 | * a 2-byte reserved field; |
| 159 | * |
| 160 | * a 6-byte destination address field; |
| 161 | * |
| 162 | * a 2-byte "local admin" field; |
| 163 | * |
| 164 | * a 6-byte source address field; |
| 165 | * |
| 166 | * followed by an 802.2 LLC header. |
| 167 | * |
| 168 | * This looks somewhat like something derived from the HIPPI-FP 4.4 |
| 169 | * Header_Area, followed an HIPPI-FP 4.4 D1_Area containing a D1 data set |
| 170 | * with the header in HIPPI-LE 3.4 (ANSI X3.218-1993), followed by an |
| 171 | * HIPPI-FP 4.4 D2_Area (with no Offset) containing the 802.2 LLC header |
| 172 | * and payload? Or does the "offsets" field contain the D2_Offset, |
| 173 | * with that many bytes of offset before the payload? |
| 174 | * |
| 175 | * See http://wotug.org/parallel/standards/hippi/ for an archive of |
| 176 | * HIPPI specifications. |
| 177 | * |
| 178 | * RFC 2067 imposes some additional restrictions. It says that the |
| 179 | * Offset is always zero |
| 180 | * |
| 181 | * HIPPI is long-gone, and the source files found in an older version |
| 182 | * of NetBSD don't appear to be in the main CVS branch, so we may never |
| 183 | * see a capture with this link-layer type. |
| 184 | */ |
| 185 | #if defined(__NetBSD__) |
| 186 | #define DLT_HIPPI 15 /* HIPPI */ |
| 187 | #endif |
| 188 | |
| 189 | /* |
| 190 | * NetBSD uses 16 for DLT_HDLC; see below. |
| 191 | * BSD/OS uses it for PPP; see above. |
| 192 | * As far as I know, no other OS uses it for anything; don't use it |
| 193 | * for anything else. |
| 194 | */ |
| 195 | |
| 196 | /* |
| 197 | * 17 was used for DLT_PFLOG in OpenBSD; it no longer is. |
| 198 | * |
| 199 | * It was DLT_LANE8023 in SuSE 6.3, so we defined LINKTYPE_PFLOG |
| 200 | * as 117 so that pflog captures would use a link-layer header type |
| 201 | * value that didn't collide with any other values. On all |
| 202 | * platforms other than OpenBSD, we defined DLT_PFLOG as 117, |
| 203 | * and we mapped between LINKTYPE_PFLOG and DLT_PFLOG. |
| 204 | * |
| 205 | * OpenBSD eventually switched to using 117 for DLT_PFLOG as well. |
| 206 | * |
| 207 | * Don't use 17 for anything else. |
| 208 | */ |
| 209 | |
| 210 | /* |
| 211 | * 18 is used for DLT_PFSYNC in OpenBSD, NetBSD, DragonFly BSD and |
| 212 | * macOS; don't use it for anything else. (FreeBSD uses 121, which |
| 213 | * collides with DLT_HHDLC, even though it doesn't use 18 for |
| 214 | * anything and doesn't appear to have ever used it for anything.) |
| 215 | * |
| 216 | * We define it as 18 on those platforms; it is, unfortunately, used |
| 217 | * for DLT_CIP in SUSE 6.3, so we don't define it as 18 on all |
| 218 | * platforms. We define it as 121 on FreeBSD and as the same |
| 219 | * value that we assigned to LINKTYPE_PFSYNC on all remaining |
| 220 | * platforms. |
| 221 | */ |
| 222 | #if defined(__OpenBSD__) || defined(__NetBSD__) || defined(__DragonFly__) || defined(__APPLE__) |
| 223 | #define DLT_PFSYNC 18 |
| 224 | #endif |
| 225 | |
| 226 | #define DLT_ATM_CLIP 19 /* Linux Classical IP over ATM */ |
| 227 | |
| 228 | /* |
| 229 | * Apparently Redback uses this for its SmartEdge 400/800. I hope |
| 230 | * nobody else decided to use it, too. |
| 231 | */ |
| 232 | #define DLT_REDBACK_SMARTEDGE 32 |
| 233 | |
| 234 | /* |
| 235 | * These values are defined by NetBSD; other platforms should refrain from |
| 236 | * using them for other purposes, so that NetBSD savefiles with link |
| 237 | * types of 50 or 51 can be read as this type on all platforms. |
| 238 | */ |
| 239 | #define DLT_PPP_SERIAL 50 /* PPP over serial with HDLC encapsulation */ |
| 240 | #define DLT_PPP_ETHER 51 /* PPP over Ethernet */ |
| 241 | |
| 242 | /* |
| 243 | * The Axent Raptor firewall - now the Symantec Enterprise Firewall - uses |
| 244 | * a link-layer type of 99 for the tcpdump it supplies. The link-layer |
| 245 | * header has 6 bytes of unknown data, something that appears to be an |
| 246 | * Ethernet type, and 36 bytes that appear to be 0 in at least one capture |
| 247 | * I've seen. |
| 248 | */ |
| 249 | #define DLT_SYMANTEC_FIREWALL 99 |
| 250 | |
| 251 | /* |
| 252 | * Values between 100 and 103 are used in capture file headers as |
| 253 | * link-layer header type LINKTYPE_ values corresponding to DLT_ types |
| 254 | * that differ between platforms; don't use those values for new DLT_ |
| 255 | * new types. |
| 256 | */ |
| 257 | |
| 258 | /* |
| 259 | * Values starting with 104 are used for newly-assigned link-layer |
| 260 | * header type values; for those link-layer header types, the DLT_ |
| 261 | * value returned by pcap_datalink() and passed to pcap_open_dead(), |
| 262 | * and the LINKTYPE_ value that appears in capture files, are the |
| 263 | * same. |
| 264 | * |
| 265 | * DLT_HIGH_MATCHING_MIN is the lowest such value; DLT_HIGH_MATCHING_MAX is |
| 266 | * the highest such value. |
| 267 | */ |
| 268 | #define DLT_HIGH_MATCHING_MIN 104 |
| 269 | |
| 270 | /* |
| 271 | * This value was defined by libpcap 0.5; platforms that have defined |
| 272 | * it with a different value should define it here with that value - |
| 273 | * a link type of 104 in a save file will be mapped to DLT_C_HDLC, |
| 274 | * whatever value that happens to be, so programs will correctly |
| 275 | * handle files with that link type regardless of the value of |
| 276 | * DLT_C_HDLC. |
| 277 | * |
| 278 | * The name DLT_C_HDLC was used by BSD/OS; we use that name for source |
| 279 | * compatibility with programs written for BSD/OS. |
| 280 | * |
| 281 | * libpcap 0.5 defined it as DLT_CHDLC; we define DLT_CHDLC as well, |
| 282 | * for source compatibility with programs written for libpcap 0.5. |
| 283 | */ |
| 284 | #define DLT_C_HDLC 104 /* Cisco HDLC */ |
| 285 | #define DLT_CHDLC DLT_C_HDLC |
| 286 | |
| 287 | #define DLT_IEEE802_11 105 /* IEEE 802.11 wireless */ |
| 288 | |
| 289 | /* |
| 290 | * 106 is reserved for Linux Classical IP over ATM; it's like DLT_RAW, |
| 291 | * except when it isn't. (I.e., sometimes it's just raw IP, and |
| 292 | * sometimes it isn't.) We currently handle it as DLT_LINUX_SLL, |
| 293 | * so that we don't have to worry about the link-layer header.) |
| 294 | */ |
| 295 | |
| 296 | /* |
| 297 | * Frame Relay; BSD/OS has a DLT_FR with a value of 11, but that collides |
| 298 | * with other values. |
| 299 | * DLT_FR and DLT_FRELAY packets start with the Q.922 Frame Relay header |
| 300 | * (DLCI, etc.). |
| 301 | */ |
| 302 | #define DLT_FRELAY 107 |
| 303 | |
| 304 | /* |
| 305 | * OpenBSD DLT_LOOP, for loopback devices; it's like DLT_NULL, except |
| 306 | * that the AF_ type in the link-layer header is in network byte order. |
| 307 | * |
| 308 | * DLT_LOOP is 12 in OpenBSD, but that's DLT_RAW in other OSes, so |
| 309 | * we don't use 12 for it in OSes other than OpenBSD; instead, we |
| 310 | * use the same value as LINKTYPE_LOOP. |
| 311 | */ |
| 312 | #ifdef __OpenBSD__ |
| 313 | #define DLT_LOOP 12 |
| 314 | #else |
| 315 | #define DLT_LOOP 108 |
| 316 | #endif |
| 317 | |
| 318 | /* |
| 319 | * Encapsulated packets for IPsec; DLT_ENC is 13 in OpenBSD, but that's |
| 320 | * DLT_SLIP_BSDOS in NetBSD, so we don't use 13 for it in OSes other |
| 321 | * than OpenBSD; instead, we use the same value as LINKTYPE_ENC. |
| 322 | */ |
| 323 | #ifdef __OpenBSD__ |
| 324 | #define DLT_ENC 13 |
| 325 | #else |
| 326 | #define DLT_ENC 109 |
| 327 | #endif |
| 328 | |
| 329 | /* |
| 330 | * Values 110 and 111 are reserved for use in capture file headers |
| 331 | * as link-layer types corresponding to DLT_ types that might differ |
| 332 | * between platforms; don't use those values for new DLT_ types |
| 333 | * other than the corresponding DLT_ types. |
| 334 | */ |
| 335 | |
| 336 | /* |
| 337 | * NetBSD uses 16 for (Cisco) "HDLC framing". For other platforms, |
| 338 | * we define it to have the same value as LINKTYPE_NETBSD_HDLC. |
| 339 | */ |
| 340 | #if defined(__NetBSD__) |
| 341 | #define DLT_HDLC 16 /* Cisco HDLC */ |
| 342 | #else |
| 343 | #define DLT_HDLC 112 |
| 344 | #endif |
| 345 | |
| 346 | /* |
| 347 | * Linux cooked sockets. |
| 348 | */ |
| 349 | #define DLT_LINUX_SLL 113 |
| 350 | |
| 351 | /* |
| 352 | * Apple LocalTalk hardware. |
| 353 | */ |
| 354 | #define DLT_LTALK 114 |
| 355 | |
| 356 | /* |
| 357 | * Acorn Econet. |
| 358 | */ |
| 359 | #define DLT_ECONET 115 |
| 360 | |
| 361 | /* |
| 362 | * Reserved for use with OpenBSD ipfilter. |
| 363 | */ |
| 364 | #define DLT_IPFILTER 116 |
| 365 | |
| 366 | /* |
| 367 | * OpenBSD DLT_PFLOG. |
| 368 | */ |
| 369 | #define DLT_PFLOG 117 |
| 370 | |
| 371 | /* |
| 372 | * Registered for Cisco-internal use. |
| 373 | */ |
| 374 | #define DLT_CISCO_IOS 118 |
| 375 | |
| 376 | /* |
| 377 | * For 802.11 cards using the Prism II chips, with a link-layer |
| 378 | * header including Prism monitor mode information plus an 802.11 |
| 379 | * header. |
| 380 | */ |
| 381 | #define DLT_PRISM_HEADER 119 |
| 382 | |
| 383 | /* |
| 384 | * Reserved for Aironet 802.11 cards, with an Aironet link-layer header |
| 385 | * (see Doug Ambrisko's FreeBSD patches). |
| 386 | */ |
| 387 | #define DLT_AIRONET_HEADER 120 |
| 388 | |
| 389 | /* |
| 390 | * Sigh. |
| 391 | * |
| 392 | * 121 was reserved for Siemens HiPath HDLC on 2002-01-25, as |
| 393 | * requested by Tomas Kukosa. |
| 394 | * |
| 395 | * On 2004-02-25, a FreeBSD checkin to sys/net/bpf.h was made that |
| 396 | * assigned 121 as DLT_PFSYNC. In current versions, its libpcap |
| 397 | * does DLT_ <-> LINKTYPE_ mapping, mapping DLT_PFSYNC to a |
| 398 | * LINKTYPE_PFSYNC value of 246, so it should write out DLT_PFSYNC |
| 399 | * dump files with 246 as the link-layer header type. (Earlier |
| 400 | * versions might not have done mapping, in which case they would |
| 401 | * have written them out with a link-layer header type of 121.) |
| 402 | * |
| 403 | * OpenBSD, from which pf came, however, uses 18 for DLT_PFSYNC; |
| 404 | * its libpcap does no DLT_ <-> LINKTYPE_ mapping, so it would |
| 405 | * write out DLT_PFSYNC dump files with use 18 as the link-layer |
| 406 | * header type. |
| 407 | * |
| 408 | * NetBSD, DragonFly BSD, and Darwin also use 18 for DLT_PFSYNC; in |
| 409 | * current versions, their libpcaps do DLT_ <-> LINKTYPE_ mapping, |
| 410 | * mapping DLT_PFSYNC to a LINKTYPE_PFSYNC value of 246, so they |
| 411 | * should write out DLT_PFSYNC dump files with 246 as the link-layer |
| 412 | * header type. (Earlier versions might not have done mapping, |
| 413 | * in which case they'd work the same way OpenBSD does, writing |
| 414 | * them out with a link-layer header type of 18.) |
| 415 | * |
| 416 | * We'll define DLT_PFSYNC as: |
| 417 | * |
| 418 | * 18 on NetBSD, OpenBSD, DragonFly BSD, and Darwin; |
| 419 | * |
| 420 | * 121 on FreeBSD; |
| 421 | * |
| 422 | * 246 everywhere else. |
| 423 | * |
| 424 | * We'll define DLT_HHDLC as 121 on everything except for FreeBSD; |
| 425 | * anybody who wants to compile, on FreeBSD, code that uses DLT_HHDLC |
| 426 | * is out of luck. |
| 427 | * |
| 428 | * We'll define LINKTYPE_PFSYNC as 246 on *all* platforms, so that |
| 429 | * savefiles written using *this* code won't use 18 or 121 for PFSYNC, |
| 430 | * they'll all use 246. |
| 431 | * |
| 432 | * Code that uses pcap_datalink() to determine the link-layer header |
| 433 | * type of a savefile won't, when built and run on FreeBSD, be able |
| 434 | * to distinguish between LINKTYPE_PFSYNC and LINKTYPE_HHDLC capture |
| 435 | * files, as pcap_datalink() will give 121 for both of them. Code |
| 436 | * that doesn't, such as the code in Wireshark, will be able to |
| 437 | * distinguish between them. |
| 438 | * |
| 439 | * FreeBSD's libpcap won't map a link-layer header type of 18 - i.e., |
| 440 | * DLT_PFSYNC files from OpenBSD and possibly older versions of NetBSD, |
| 441 | * DragonFly BSD, and macOS - to DLT_PFSYNC, so code built with FreeBSD's |
| 442 | * libpcap won't treat those files as DLT_PFSYNC files. |
| 443 | * |
| 444 | * Other libpcaps won't map a link-layer header type of 121 to DLT_PFSYNC; |
| 445 | * this means they can read DLT_HHDLC files, if any exist, but won't |
| 446 | * treat pcap files written by any older versions of FreeBSD libpcap that |
| 447 | * didn't map to 246 as DLT_PFSYNC files. |
| 448 | */ |
| 449 | #ifdef __FreeBSD__ |
| 450 | #define DLT_PFSYNC 121 |
| 451 | #else |
| 452 | #define DLT_HHDLC 121 |
| 453 | #endif |
| 454 | |
| 455 | /* |
| 456 | * This is for RFC 2625 IP-over-Fibre Channel. |
| 457 | * |
| 458 | * This is not for use with raw Fibre Channel, where the link-layer |
| 459 | * header starts with a Fibre Channel frame header; it's for IP-over-FC, |
| 460 | * where the link-layer header starts with an RFC 2625 Network_Header |
| 461 | * field. |
| 462 | */ |
| 463 | #define DLT_IP_OVER_FC 122 |
| 464 | |
| 465 | /* |
| 466 | * This is for Full Frontal ATM on Solaris with SunATM, with a |
| 467 | * pseudo-header followed by an AALn PDU. |
| 468 | * |
| 469 | * There may be other forms of Full Frontal ATM on other OSes, |
| 470 | * with different pseudo-headers. |
| 471 | * |
| 472 | * If ATM software returns a pseudo-header with VPI/VCI information |
| 473 | * (and, ideally, packet type information, e.g. signalling, ILMI, |
| 474 | * LANE, LLC-multiplexed traffic, etc.), it should not use |
| 475 | * DLT_ATM_RFC1483, but should get a new DLT_ value, so tcpdump |
| 476 | * and the like don't have to infer the presence or absence of a |
| 477 | * pseudo-header and the form of the pseudo-header. |
| 478 | */ |
| 479 | #define DLT_SUNATM 123 /* Solaris+SunATM */ |
| 480 | |
| 481 | /* |
| 482 | * Reserved as per request from Kent Dahlgren <kent@praesum.com> |
| 483 | * for private use. |
| 484 | */ |
| 485 | #define DLT_RIO 124 /* RapidIO */ |
| 486 | #define DLT_PCI_EXP 125 /* PCI Express */ |
| 487 | #define DLT_AURORA 126 /* Xilinx Aurora link layer */ |
| 488 | |
| 489 | /* |
| 490 | * Header for 802.11 plus a number of bits of link-layer information |
| 491 | * including radio information, used by some recent BSD drivers as |
| 492 | * well as the madwifi Atheros driver for Linux. |
| 493 | */ |
| 494 | #define DLT_IEEE802_11_RADIO 127 /* 802.11 plus radiotap radio header */ |
| 495 | |
| 496 | /* |
| 497 | * Reserved for the TZSP encapsulation, as per request from |
| 498 | * Chris Waters <chris.waters@networkchemistry.com> |
| 499 | * TZSP is a generic encapsulation for any other link type, |
| 500 | * which includes a means to include meta-information |
| 501 | * with the packet, e.g. signal strength and channel |
| 502 | * for 802.11 packets. |
| 503 | */ |
| 504 | #define DLT_TZSP 128 /* Tazmen Sniffer Protocol */ |
| 505 | |
| 506 | /* |
| 507 | * BSD's ARCNET headers have the source host, destination host, |
| 508 | * and type at the beginning of the packet; that's what's handed |
| 509 | * up to userland via BPF. |
| 510 | * |
| 511 | * Linux's ARCNET headers, however, have a 2-byte offset field |
| 512 | * between the host IDs and the type; that's what's handed up |
| 513 | * to userland via PF_PACKET sockets. |
| 514 | * |
| 515 | * We therefore have to have separate DLT_ values for them. |
| 516 | */ |
| 517 | #define DLT_ARCNET_LINUX 129 /* ARCNET */ |
| 518 | |
| 519 | /* |
| 520 | * Juniper-private data link types, as per request from |
| 521 | * Hannes Gredler <hannes@juniper.net>. The DLT_s are used |
| 522 | * for passing on chassis-internal metainformation such as |
| 523 | * QOS profiles, etc.. |
| 524 | */ |
| 525 | #define DLT_JUNIPER_MLPPP 130 |
| 526 | #define DLT_JUNIPER_MLFR 131 |
| 527 | #define DLT_JUNIPER_ES 132 |
| 528 | #define DLT_JUNIPER_GGSN 133 |
| 529 | #define DLT_JUNIPER_MFR 134 |
| 530 | #define DLT_JUNIPER_ATM2 135 |
| 531 | #define DLT_JUNIPER_SERVICES 136 |
| 532 | #define DLT_JUNIPER_ATM1 137 |
| 533 | |
| 534 | /* |
| 535 | * Apple IP-over-IEEE 1394, as per a request from Dieter Siegmund |
| 536 | * <dieter@apple.com>. The header that's presented is an Ethernet-like |
| 537 | * header: |
| 538 | * |
| 539 | * #define FIREWIRE_EUI64_LEN 8 |
| 540 | * struct firewire_header { |
| 541 | * u_char firewire_dhost[FIREWIRE_EUI64_LEN]; |
| 542 | * u_char firewire_shost[FIREWIRE_EUI64_LEN]; |
| 543 | * u_short firewire_type; |
| 544 | * }; |
| 545 | * |
| 546 | * with "firewire_type" being an Ethernet type value, rather than, |
| 547 | * for example, raw GASP frames being handed up. |
| 548 | */ |
| 549 | #define DLT_APPLE_IP_OVER_IEEE1394 138 |
| 550 | |
| 551 | /* |
| 552 | * Various SS7 encapsulations, as per a request from Jeff Morriss |
| 553 | * <jeff.morriss[AT]ulticom.com> and subsequent discussions. |
| 554 | */ |
| 555 | #define DLT_MTP2_WITH_PHDR 139 /* pseudo-header with various info, followed by MTP2 */ |
| 556 | #define DLT_MTP2 140 /* MTP2, without pseudo-header */ |
| 557 | #define DLT_MTP3 141 /* MTP3, without pseudo-header or MTP2 */ |
| 558 | #define DLT_SCCP 142 /* SCCP, without pseudo-header or MTP2 or MTP3 */ |
| 559 | |
| 560 | /* |
| 561 | * DOCSIS MAC frames. |
| 562 | */ |
| 563 | #define DLT_DOCSIS 143 |
| 564 | |
| 565 | /* |
| 566 | * Linux-IrDA packets. Protocol defined at https://www.irda.org. |
| 567 | * Those packets include IrLAP headers and above (IrLMP...), but |
| 568 | * don't include Phy framing (SOF/EOF/CRC & byte stuffing), because Phy |
| 569 | * framing can be handled by the hardware and depend on the bitrate. |
| 570 | * This is exactly the format you would get capturing on a Linux-IrDA |
| 571 | * interface (irdaX), but not on a raw serial port. |
| 572 | * Note the capture is done in "Linux-cooked" mode, so each packet include |
| 573 | * a fake packet header (struct sll_header). This is because IrDA packet |
| 574 | * decoding is dependent on the direction of the packet (incoming or |
| 575 | * outgoing). |
| 576 | * When/if other platform implement IrDA capture, we may revisit the |
| 577 | * issue and define a real DLT_IRDA... |
| 578 | * Jean II |
| 579 | */ |
| 580 | #define DLT_LINUX_IRDA 144 |
| 581 | |
| 582 | /* |
| 583 | * Reserved for IBM SP switch and IBM Next Federation switch. |
| 584 | */ |
| 585 | #define DLT_IBM_SP 145 |
| 586 | #define DLT_IBM_SN 146 |
| 587 | |
| 588 | /* |
| 589 | * Reserved for private use. If you have some link-layer header type |
| 590 | * that you want to use within your organization, with the capture files |
| 591 | * using that link-layer header type not ever be sent outside your |
| 592 | * organization, you can use these values. |
| 593 | * |
| 594 | * No libpcap release will use these for any purpose, nor will any |
| 595 | * tcpdump release use them, either. |
| 596 | * |
| 597 | * Do *NOT* use these in capture files that you expect anybody not using |
| 598 | * your private versions of capture-file-reading tools to read; in |
| 599 | * particular, do *NOT* use them in products, otherwise you may find that |
| 600 | * people won't be able to use tcpdump, or snort, or Ethereal, or... to |
| 601 | * read capture files from your firewall/intrusion detection/traffic |
| 602 | * monitoring/etc. appliance, or whatever product uses that DLT_ value, |
| 603 | * and you may also find that the developers of those applications will |
| 604 | * not accept patches to let them read those files. |
| 605 | * |
| 606 | * Also, do not use them if somebody might send you a capture using them |
| 607 | * for *their* private type and tools using them for *your* private type |
| 608 | * would have to read them. |
| 609 | * |
| 610 | * Instead, ask "tcpdump-workers@lists.tcpdump.org" for a new DLT_ value, |
| 611 | * as per the comment above, and use the type you're given. |
| 612 | */ |
| 613 | #define DLT_USER0 147 |
| 614 | #define DLT_USER1 148 |
| 615 | #define DLT_USER2 149 |
| 616 | #define DLT_USER3 150 |
| 617 | #define DLT_USER4 151 |
| 618 | #define DLT_USER5 152 |
| 619 | #define DLT_USER6 153 |
| 620 | #define DLT_USER7 154 |
| 621 | #define DLT_USER8 155 |
| 622 | #define DLT_USER9 156 |
| 623 | #define DLT_USER10 157 |
| 624 | #define DLT_USER11 158 |
| 625 | #define DLT_USER12 159 |
| 626 | #define DLT_USER13 160 |
| 627 | #define DLT_USER14 161 |
| 628 | #define DLT_USER15 162 |
| 629 | |
| 630 | /* |
| 631 | * For future use with 802.11 captures - defined by AbsoluteValue |
| 632 | * Systems to store a number of bits of link-layer information |
| 633 | * including radio information: |
| 634 | * |
| 635 | * http://www.shaftnet.org/~pizza/software/capturefrm.txt |
| 636 | * |
| 637 | * but it might be used by some non-AVS drivers now or in the |
| 638 | * future. |
| 639 | */ |
| 640 | #define DLT_IEEE802_11_RADIO_AVS 163 /* 802.11 plus AVS radio header */ |
| 641 | |
| 642 | /* |
| 643 | * Juniper-private data link type, as per request from |
| 644 | * Hannes Gredler <hannes@juniper.net>. The DLT_s are used |
| 645 | * for passing on chassis-internal metainformation such as |
| 646 | * QOS profiles, etc.. |
| 647 | */ |
| 648 | #define DLT_JUNIPER_MONITOR 164 |
| 649 | |
| 650 | /* |
| 651 | * BACnet MS/TP frames. |
| 652 | */ |
| 653 | #define DLT_BACNET_MS_TP 165 |
| 654 | |
| 655 | /* |
| 656 | * Another PPP variant as per request from Karsten Keil <kkeil@suse.de>. |
| 657 | * |
| 658 | * This is used in some OSes to allow a kernel socket filter to distinguish |
| 659 | * between incoming and outgoing packets, on a socket intended to |
| 660 | * supply pppd with outgoing packets so it can do dial-on-demand and |
| 661 | * hangup-on-lack-of-demand; incoming packets are filtered out so they |
| 662 | * don't cause pppd to hold the connection up (you don't want random |
| 663 | * input packets such as port scans, packets from old lost connections, |
| 664 | * etc. to force the connection to stay up). |
| 665 | * |
| 666 | * The first byte of the PPP header (0xff03) is modified to accommodate |
| 667 | * the direction - 0x00 = IN, 0x01 = OUT. |
| 668 | */ |
| 669 | #define DLT_PPP_PPPD 166 |
| 670 | |
| 671 | /* |
| 672 | * Names for backwards compatibility with older versions of some PPP |
| 673 | * software; new software should use DLT_PPP_PPPD. |
| 674 | */ |
| 675 | #define DLT_PPP_WITH_DIRECTION DLT_PPP_PPPD |
| 676 | #define DLT_LINUX_PPP_WITHDIRECTION DLT_PPP_PPPD |
| 677 | |
| 678 | /* |
| 679 | * Juniper-private data link type, as per request from |
| 680 | * Hannes Gredler <hannes@juniper.net>. The DLT_s are used |
| 681 | * for passing on chassis-internal metainformation such as |
| 682 | * QOS profiles, cookies, etc.. |
| 683 | */ |
| 684 | #define DLT_JUNIPER_PPPOE 167 |
| 685 | #define DLT_JUNIPER_PPPOE_ATM 168 |
| 686 | |
| 687 | #define DLT_GPRS_LLC 169 /* GPRS LLC */ |
| 688 | #define DLT_GPF_T 170 /* GPF-T (ITU-T G.7041/Y.1303) */ |
| 689 | #define DLT_GPF_F 171 /* GPF-F (ITU-T G.7041/Y.1303) */ |
| 690 | |
| 691 | /* |
| 692 | * Requested by Oolan Zimmer <oz@gcom.com> for use in Gcom's T1/E1 line |
| 693 | * monitoring equipment. |
| 694 | */ |
| 695 | #define DLT_GCOM_T1E1 172 |
| 696 | #define DLT_GCOM_SERIAL 173 |
| 697 | |
| 698 | /* |
| 699 | * Juniper-private data link type, as per request from |
| 700 | * Hannes Gredler <hannes@juniper.net>. The DLT_ is used |
| 701 | * for internal communication to Physical Interface Cards (PIC) |
| 702 | */ |
| 703 | #define DLT_JUNIPER_PIC_PEER 174 |
| 704 | |
| 705 | /* |
| 706 | * Link types requested by Gregor Maier <gregor@endace.com> of Endace |
| 707 | * Measurement Systems. They add an ERF header (see |
| 708 | * https://www.endace.com/support/EndaceRecordFormat.pdf) in front of |
| 709 | * the link-layer header. |
| 710 | */ |
| 711 | #define DLT_ERF_ETH 175 /* Ethernet */ |
| 712 | #define DLT_ERF_POS 176 /* Packet-over-SONET */ |
| 713 | |
| 714 | /* |
| 715 | * Requested by Daniele Orlandi <daniele@orlandi.com> for raw LAPD |
| 716 | * for vISDN (http://www.orlandi.com/visdn/). Its link-layer header |
| 717 | * includes additional information before the LAPD header, so it's |
| 718 | * not necessarily a generic LAPD header. |
| 719 | */ |
| 720 | #define DLT_LINUX_LAPD 177 |
| 721 | |
| 722 | /* |
| 723 | * Juniper-private data link type, as per request from |
| 724 | * Hannes Gredler <hannes@juniper.net>. |
| 725 | * The DLT_ are used for prepending meta-information |
| 726 | * like interface index, interface name |
| 727 | * before standard Ethernet, PPP, Frelay & C-HDLC Frames |
| 728 | */ |
| 729 | #define DLT_JUNIPER_ETHER 178 |
| 730 | #define DLT_JUNIPER_PPP 179 |
| 731 | #define DLT_JUNIPER_FRELAY 180 |
| 732 | #define DLT_JUNIPER_CHDLC 181 |
| 733 | |
| 734 | /* |
| 735 | * Multi Link Frame Relay (FRF.16) |
| 736 | */ |
| 737 | #define DLT_MFR 182 |
| 738 | |
| 739 | /* |
| 740 | * Juniper-private data link type, as per request from |
| 741 | * Hannes Gredler <hannes@juniper.net>. |
| 742 | * The DLT_ is used for internal communication with a |
| 743 | * voice Adapter Card (PIC) |
| 744 | */ |
| 745 | #define DLT_JUNIPER_VP 183 |
| 746 | |
| 747 | /* |
| 748 | * Arinc 429 frames. |
| 749 | * DLT_ requested by Gianluca Varenni <gianluca.varenni@cacetech.com>. |
| 750 | * Every frame contains a 32bit A429 label. |
| 751 | * More documentation on Arinc 429 can be found at |
| 752 | * https://web.archive.org/web/20040616233302/https://www.condoreng.com/support/downloads/tutorials/ARINCTutorial.pdf |
| 753 | */ |
| 754 | #define DLT_A429 184 |
| 755 | |
| 756 | /* |
| 757 | * Arinc 653 Interpartition Communication messages. |
| 758 | * DLT_ requested by Gianluca Varenni <gianluca.varenni@cacetech.com>. |
| 759 | * Please refer to the A653-1 standard for more information. |
| 760 | */ |
| 761 | #define DLT_A653_ICM 185 |
| 762 | |
| 763 | /* |
| 764 | * This used to be "USB packets, beginning with a USB setup header; |
| 765 | * requested by Paolo Abeni <paolo.abeni@email.it>." |
| 766 | * |
| 767 | * However, that header didn't work all that well - it left out some |
| 768 | * useful information - and was abandoned in favor of the DLT_USB_LINUX |
| 769 | * header. |
| 770 | * |
| 771 | * This is now used by FreeBSD for its BPF taps for USB; that has its |
| 772 | * own headers. So it is written, so it is done. |
| 773 | * |
| 774 | * For source-code compatibility, we also define DLT_USB to have this |
| 775 | * value. We do it numerically so that, if code that includes this |
| 776 | * file (directly or indirectly) also includes an OS header that also |
| 777 | * defines DLT_USB as 186, we don't get a redefinition warning. |
| 778 | * (NetBSD 7 does that.) |
| 779 | */ |
| 780 | #define DLT_USB_FREEBSD 186 |
| 781 | #define DLT_USB 186 |
| 782 | |
| 783 | /* |
| 784 | * Bluetooth HCI UART transport layer (part H:4); requested by |
| 785 | * Paolo Abeni. |
| 786 | */ |
| 787 | #define DLT_BLUETOOTH_HCI_H4 187 |
| 788 | |
| 789 | /* |
| 790 | * IEEE 802.16 MAC Common Part Sublayer; requested by Maria Cruz |
| 791 | * <cruz_petagay@bah.com>. |
| 792 | */ |
| 793 | #define DLT_IEEE802_16_MAC_CPS 188 |
| 794 | |
| 795 | /* |
| 796 | * USB packets, beginning with a Linux USB header; requested by |
| 797 | * Paolo Abeni <paolo.abeni@email.it>. |
| 798 | */ |
| 799 | #define DLT_USB_LINUX 189 |
| 800 | |
| 801 | /* |
| 802 | * Controller Area Network (CAN) v. 2.0B packets. |
| 803 | * DLT_ requested by Gianluca Varenni <gianluca.varenni@cacetech.com>. |
| 804 | * Used to dump CAN packets coming from a CAN Vector board. |
| 805 | * More documentation on the CAN v2.0B frames can be found at |
| 806 | * http://www.can-cia.org/downloads/?269 |
| 807 | */ |
| 808 | #define DLT_CAN20B 190 |
| 809 | |
| 810 | /* |
| 811 | * IEEE 802.15.4, with address fields padded, as is done by Linux |
| 812 | * drivers; requested by Juergen Schimmer. |
| 813 | */ |
| 814 | #define DLT_IEEE802_15_4_LINUX 191 |
| 815 | |
| 816 | /* |
| 817 | * Per Packet Information encapsulated packets. |
| 818 | * DLT_ requested by Gianluca Varenni <gianluca.varenni@cacetech.com>. |
| 819 | */ |
| 820 | #define DLT_PPI 192 |
| 821 | |
| 822 | /* |
| 823 | * Header for 802.16 MAC Common Part Sublayer plus a radiotap radio header; |
| 824 | * requested by Charles Clancy. |
| 825 | */ |
| 826 | #define DLT_IEEE802_16_MAC_CPS_RADIO 193 |
| 827 | |
| 828 | /* |
| 829 | * Juniper-private data link type, as per request from |
| 830 | * Hannes Gredler <hannes@juniper.net>. |
| 831 | * The DLT_ is used for internal communication with a |
| 832 | * integrated service module (ISM). |
| 833 | */ |
| 834 | #define DLT_JUNIPER_ISM 194 |
| 835 | |
| 836 | /* |
| 837 | * IEEE 802.15.4, exactly as it appears in the spec (no padding, no |
| 838 | * nothing); requested by Mikko Saarnivala <mikko.saarnivala@sensinode.com>. |
| 839 | * For this one, we expect the FCS to be present at the end of the frame; |
| 840 | * if the frame has no FCS, DLT_IEEE802_15_4_NOFCS should be used. |
| 841 | * |
| 842 | * We keep the name DLT_IEEE802_15_4 as an alias for backwards |
| 843 | * compatibility, but, again, this should *only* be used for 802.15.4 |
| 844 | * frames that include the FCS. |
| 845 | */ |
| 846 | #define DLT_IEEE802_15_4_WITHFCS 195 |
| 847 | #define DLT_IEEE802_15_4 DLT_IEEE802_15_4_WITHFCS |
| 848 | |
| 849 | /* |
| 850 | * Various link-layer types, with a pseudo-header, for SITA |
| 851 | * (https://www.sita.aero/); requested by Fulko Hew (fulko.hew@gmail.com). |
| 852 | */ |
| 853 | #define DLT_SITA 196 |
| 854 | |
| 855 | /* |
| 856 | * Various link-layer types, with a pseudo-header, for Endace DAG cards; |
| 857 | * encapsulates Endace ERF records. Requested by Stephen Donnelly |
| 858 | * <stephen@endace.com>. |
| 859 | */ |
| 860 | #define DLT_ERF 197 |
| 861 | |
| 862 | /* |
| 863 | * Special header prepended to Ethernet packets when capturing from a |
| 864 | * u10 Networks board. Requested by Phil Mulholland |
| 865 | * <phil@u10networks.com>. |
| 866 | */ |
| 867 | #define DLT_RAIF1 198 |
| 868 | |
| 869 | /* |
| 870 | * IPMB packet for IPMI, beginning with a 2-byte header, followed by |
| 871 | * the I2C slave address, followed by the netFn and LUN, etc.. |
| 872 | * Requested by Chanthy Toeung <chanthy.toeung@ca.kontron.com>. |
| 873 | * |
| 874 | * XXX - this used to be called DLT_IPMB, back when we got the |
| 875 | * impression from the email thread requesting it that the packet |
| 876 | * had no extra 2-byte header. We've renamed it; if anybody used |
| 877 | * DLT_IPMB and assumed no 2-byte header, this will cause the compile |
| 878 | * to fail, at which point we'll have to figure out what to do about |
| 879 | * the two header types using the same DLT_/LINKTYPE_ value. If that |
| 880 | * doesn't happen, we'll assume nobody used it and that the redefinition |
| 881 | * is safe. |
| 882 | */ |
| 883 | #define DLT_IPMB_KONTRON 199 |
| 884 | |
| 885 | /* |
| 886 | * Juniper-private data link type, as per request from |
| 887 | * Hannes Gredler <hannes@juniper.net>. |
| 888 | * The DLT_ is used for capturing data on a secure tunnel interface. |
| 889 | */ |
| 890 | #define DLT_JUNIPER_ST 200 |
| 891 | |
| 892 | /* |
| 893 | * Bluetooth HCI UART transport layer (part H:4), with pseudo-header |
| 894 | * that includes direction information; requested by Paolo Abeni. |
| 895 | */ |
| 896 | #define DLT_BLUETOOTH_HCI_H4_WITH_PHDR 201 |
| 897 | |
| 898 | /* |
| 899 | * AX.25 packet with a 1-byte KISS header; see |
| 900 | * |
| 901 | * http://www.ax25.net/kiss.htm |
| 902 | * |
| 903 | * as per Richard Stearn <richard@rns-stearn.demon.co.uk>. |
| 904 | */ |
| 905 | #define DLT_AX25_KISS 202 |
| 906 | |
| 907 | /* |
| 908 | * LAPD packets from an ISDN channel, starting with the address field, |
| 909 | * with no pseudo-header. |
| 910 | * Requested by Varuna De Silva <varunax@gmail.com>. |
| 911 | */ |
| 912 | #define DLT_LAPD 203 |
| 913 | |
| 914 | /* |
| 915 | * PPP, with a one-byte direction pseudo-header prepended - zero means |
| 916 | * "received by this host", non-zero (any non-zero value) means "sent by |
| 917 | * this host" - as per Will Barker <w.barker@zen.co.uk>. |
| 918 | * |
| 919 | * Don't confuse this with DLT_PPP_WITH_DIRECTION, which is an old |
| 920 | * name for what is now called DLT_PPP_PPPD. |
| 921 | */ |
| 922 | #define DLT_PPP_WITH_DIR 204 |
| 923 | |
| 924 | /* |
| 925 | * Cisco HDLC, with a one-byte direction pseudo-header prepended - zero |
| 926 | * means "received by this host", non-zero (any non-zero value) means |
| 927 | * "sent by this host" - as per Will Barker <w.barker@zen.co.uk>. |
| 928 | */ |
| 929 | #define DLT_C_HDLC_WITH_DIR 205 |
| 930 | |
| 931 | /* |
| 932 | * Frame Relay, with a one-byte direction pseudo-header prepended - zero |
| 933 | * means "received by this host" (DCE -> DTE), non-zero (any non-zero |
| 934 | * value) means "sent by this host" (DTE -> DCE) - as per Will Barker |
| 935 | * <w.barker@zen.co.uk>. |
| 936 | */ |
| 937 | #define DLT_FRELAY_WITH_DIR 206 |
| 938 | |
| 939 | /* |
| 940 | * LAPB, with a one-byte direction pseudo-header prepended - zero means |
| 941 | * "received by this host" (DCE -> DTE), non-zero (any non-zero value) |
| 942 | * means "sent by this host" (DTE -> DCE)- as per Will Barker |
| 943 | * <w.barker@zen.co.uk>. |
| 944 | */ |
| 945 | #define DLT_LAPB_WITH_DIR 207 |
| 946 | |
| 947 | /* |
| 948 | * 208 is reserved for an as-yet-unspecified proprietary link-layer |
| 949 | * type, as requested by Will Barker. |
| 950 | */ |
| 951 | |
| 952 | /* |
| 953 | * IPMB with a Linux-specific pseudo-header; as requested by Alexey Neyman |
| 954 | * <avn@pigeonpoint.com>. |
| 955 | */ |
| 956 | #define DLT_IPMB_LINUX 209 |
| 957 | |
| 958 | /* |
| 959 | * FlexRay automotive bus - http://www.flexray.com/ - as requested |
| 960 | * by Hannes Kaelber <hannes.kaelber@x2e.de>. |
| 961 | */ |
| 962 | #define DLT_FLEXRAY 210 |
| 963 | |
| 964 | /* |
| 965 | * Media Oriented Systems Transport (MOST) bus for multimedia |
| 966 | * transport - https://www.mostcooperation.com/ - as requested |
| 967 | * by Hannes Kaelber <hannes.kaelber@x2e.de>. |
| 968 | */ |
| 969 | #define DLT_MOST 211 |
| 970 | |
| 971 | /* |
| 972 | * Local Interconnect Network (LIN) bus for vehicle networks - |
| 973 | * http://www.lin-subbus.org/ - as requested by Hannes Kaelber |
| 974 | * <hannes.kaelber@x2e.de>. |
| 975 | */ |
| 976 | #define DLT_LIN 212 |
| 977 | |
| 978 | /* |
| 979 | * X2E-private data link type used for serial line capture, |
| 980 | * as requested by Hannes Kaelber <hannes.kaelber@x2e.de>. |
| 981 | */ |
| 982 | #define DLT_X2E_SERIAL 213 |
| 983 | |
| 984 | /* |
| 985 | * X2E-private data link type used for the Xoraya data logger |
| 986 | * family, as requested by Hannes Kaelber <hannes.kaelber@x2e.de>. |
| 987 | */ |
| 988 | #define DLT_X2E_XORAYA 214 |
| 989 | |
| 990 | /* |
| 991 | * IEEE 802.15.4, exactly as it appears in the spec (no padding, no |
| 992 | * nothing), but with the PHY-level data for non-ASK PHYs (4 octets |
| 993 | * of 0 as preamble, one octet of SFD, one octet of frame length+ |
| 994 | * reserved bit, and then the MAC-layer data, starting with the |
| 995 | * frame control field). |
| 996 | * |
| 997 | * Requested by Max Filippov <jcmvbkbc@gmail.com>. |
| 998 | */ |
| 999 | #define DLT_IEEE802_15_4_NONASK_PHY 215 |
| 1000 | |
| 1001 | /* |
| 1002 | * David Gibson <david@gibson.dropbear.id.au> requested this for |
| 1003 | * captures from the Linux kernel /dev/input/eventN devices. This |
| 1004 | * is used to communicate keystrokes and mouse movements from the |
| 1005 | * Linux kernel to display systems, such as Xorg. |
| 1006 | */ |
| 1007 | #define DLT_LINUX_EVDEV 216 |
| 1008 | |
| 1009 | /* |
| 1010 | * GSM Um and Abis interfaces, preceded by a "gsmtap" header. |
| 1011 | * |
| 1012 | * Requested by Harald Welte <laforge@gnumonks.org>. |
| 1013 | */ |
| 1014 | #define DLT_GSMTAP_UM 217 |
| 1015 | #define DLT_GSMTAP_ABIS 218 |
| 1016 | |
| 1017 | /* |
| 1018 | * MPLS, with an MPLS label as the link-layer header. |
| 1019 | * Requested by Michele Marchetto <michele@openbsd.org> on behalf |
| 1020 | * of OpenBSD. |
| 1021 | */ |
| 1022 | #define DLT_MPLS 219 |
| 1023 | |
| 1024 | /* |
| 1025 | * USB packets, beginning with a Linux USB header, with the USB header |
| 1026 | * padded to 64 bytes; required for memory-mapped access. |
| 1027 | */ |
| 1028 | #define DLT_USB_LINUX_MMAPPED 220 |
| 1029 | |
| 1030 | /* |
| 1031 | * DECT packets, with a pseudo-header; requested by |
| 1032 | * Matthias Wenzel <tcpdump@mazzoo.de>. |
| 1033 | */ |
| 1034 | #define DLT_DECT 221 |
| 1035 | |
| 1036 | /* |
| 1037 | * From: "Lidwa, Eric (GSFC-582.0)[SGT INC]" <eric.lidwa-1@nasa.gov> |
| 1038 | * Date: Mon, 11 May 2009 11:18:30 -0500 |
| 1039 | * |
| 1040 | * DLT_AOS. We need it for AOS Space Data Link Protocol. |
| 1041 | * I have already written dissectors for but need an OK from |
| 1042 | * legal before I can submit a patch. |
| 1043 | * |
| 1044 | */ |
| 1045 | #define DLT_AOS 222 |
| 1046 | |
| 1047 | /* |
| 1048 | * WirelessHART (Highway Addressable Remote Transducer) |
| 1049 | * From the HART Communication Foundation |
| 1050 | * IEC/PAS 62591 |
| 1051 | * |
| 1052 | * Requested by Sam Roberts <vieuxtech@gmail.com>. |
| 1053 | */ |
| 1054 | #define DLT_WIHART 223 |
| 1055 | |
| 1056 | /* |
| 1057 | * Fibre Channel FC-2 frames, beginning with a Frame_Header. |
| 1058 | * Requested by Kahou Lei <kahou82@gmail.com>. |
| 1059 | */ |
| 1060 | #define DLT_FC_2 224 |
| 1061 | |
| 1062 | /* |
| 1063 | * Fibre Channel FC-2 frames, beginning with an encoding of the |
| 1064 | * SOF, and ending with an encoding of the EOF. |
| 1065 | * |
| 1066 | * The encodings represent the frame delimiters as 4-byte sequences |
| 1067 | * representing the corresponding ordered sets, with K28.5 |
| 1068 | * represented as 0xBC, and the D symbols as the corresponding |
| 1069 | * byte values; for example, SOFi2, which is K28.5 - D21.5 - D1.2 - D21.2, |
| 1070 | * is represented as 0xBC 0xB5 0x55 0x55. |
| 1071 | * |
| 1072 | * Requested by Kahou Lei <kahou82@gmail.com>. |
| 1073 | */ |
| 1074 | #define DLT_FC_2_WITH_FRAME_DELIMS 225 |
| 1075 | |
| 1076 | /* |
| 1077 | * Solaris ipnet pseudo-header; requested by Darren Reed <Darren.Reed@Sun.COM>. |
| 1078 | * |
| 1079 | * The pseudo-header starts with a one-byte version number; for version 2, |
| 1080 | * the pseudo-header is: |
| 1081 | * |
| 1082 | * struct dl_ipnetinfo { |
| 1083 | * uint8_t dli_version; |
| 1084 | * uint8_t dli_family; |
| 1085 | * uint16_t dli_htype; |
| 1086 | * uint32_t dli_pktlen; |
| 1087 | * uint32_t dli_ifindex; |
| 1088 | * uint32_t dli_grifindex; |
| 1089 | * uint32_t dli_zsrc; |
| 1090 | * uint32_t dli_zdst; |
| 1091 | * }; |
| 1092 | * |
| 1093 | * dli_version is 2 for the current version of the pseudo-header. |
| 1094 | * |
| 1095 | * dli_family is a Solaris address family value, so it's 2 for IPv4 |
| 1096 | * and 26 for IPv6. |
| 1097 | * |
| 1098 | * dli_htype is a "hook type" - 0 for incoming packets, 1 for outgoing |
| 1099 | * packets, and 2 for packets arriving from another zone on the same |
| 1100 | * machine. |
| 1101 | * |
| 1102 | * dli_pktlen is the length of the packet data following the pseudo-header |
| 1103 | * (so the captured length minus dli_pktlen is the length of the |
| 1104 | * pseudo-header, assuming the entire pseudo-header was captured). |
| 1105 | * |
| 1106 | * dli_ifindex is the interface index of the interface on which the |
| 1107 | * packet arrived. |
| 1108 | * |
| 1109 | * dli_grifindex is the group interface index number (for IPMP interfaces). |
| 1110 | * |
| 1111 | * dli_zsrc is the zone identifier for the source of the packet. |
| 1112 | * |
| 1113 | * dli_zdst is the zone identifier for the destination of the packet. |
| 1114 | * |
| 1115 | * A zone number of 0 is the global zone; a zone number of 0xffffffff |
| 1116 | * means that the packet arrived from another host on the network, not |
| 1117 | * from another zone on the same machine. |
| 1118 | * |
| 1119 | * An IPv4 or IPv6 datagram follows the pseudo-header; dli_family indicates |
| 1120 | * which of those it is. |
| 1121 | */ |
| 1122 | #define DLT_IPNET 226 |
| 1123 | |
| 1124 | /* |
| 1125 | * CAN (Controller Area Network) frames, with a pseudo-header as supplied |
| 1126 | * by Linux SocketCAN, and with multi-byte numerical fields in that header |
| 1127 | * in big-endian byte order. |
| 1128 | * |
| 1129 | * See Documentation/networking/can.txt in the Linux source. |
| 1130 | * |
| 1131 | * Requested by Felix Obenhuber <felix@obenhuber.de>. |
| 1132 | */ |
| 1133 | #define DLT_CAN_SOCKETCAN 227 |
| 1134 | |
| 1135 | /* |
| 1136 | * Raw IPv4/IPv6; different from DLT_RAW in that the DLT_ value specifies |
| 1137 | * whether it's v4 or v6. Requested by Darren Reed <Darren.Reed@Sun.COM>. |
| 1138 | */ |
| 1139 | #define DLT_IPV4 228 |
| 1140 | #define DLT_IPV6 229 |
| 1141 | |
| 1142 | /* |
| 1143 | * IEEE 802.15.4, exactly as it appears in the spec (no padding, no |
| 1144 | * nothing), and with no FCS at the end of the frame; requested by |
| 1145 | * Jon Smirl <jonsmirl@gmail.com>. |
| 1146 | */ |
| 1147 | #define DLT_IEEE802_15_4_NOFCS 230 |
| 1148 | |
| 1149 | /* |
| 1150 | * Raw D-Bus: |
| 1151 | * |
| 1152 | * https://www.freedesktop.org/wiki/Software/dbus |
| 1153 | * |
| 1154 | * messages: |
| 1155 | * |
| 1156 | * https://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-messages |
| 1157 | * |
| 1158 | * starting with the endianness flag, followed by the message type, etc., |
| 1159 | * but without the authentication handshake before the message sequence: |
| 1160 | * |
| 1161 | * https://dbus.freedesktop.org/doc/dbus-specification.html#auth-protocol |
| 1162 | * |
| 1163 | * Requested by Martin Vidner <martin@vidner.net>. |
| 1164 | */ |
| 1165 | #define DLT_DBUS 231 |
| 1166 | |
| 1167 | /* |
| 1168 | * Juniper-private data link type, as per request from |
| 1169 | * Hannes Gredler <hannes@juniper.net>. |
| 1170 | */ |
| 1171 | #define DLT_JUNIPER_VS 232 |
| 1172 | #define DLT_JUNIPER_SRX_E2E 233 |
| 1173 | #define DLT_JUNIPER_FIBRECHANNEL 234 |
| 1174 | |
| 1175 | /* |
| 1176 | * DVB-CI (DVB Common Interface for communication between a PC Card |
| 1177 | * module and a DVB receiver). See |
| 1178 | * |
| 1179 | * https://www.kaiser.cx/pcap-dvbci.html |
| 1180 | * |
| 1181 | * for the specification. |
| 1182 | * |
| 1183 | * Requested by Martin Kaiser <martin@kaiser.cx>. |
| 1184 | */ |
| 1185 | #define DLT_DVB_CI 235 |
| 1186 | |
| 1187 | /* |
| 1188 | * Variant of 3GPP TS 27.010 multiplexing protocol (similar to, but |
| 1189 | * *not* the same as, 27.010). Requested by Hans-Christoph Schemmel |
| 1190 | * <hans-christoph.schemmel@cinterion.com>. |
| 1191 | */ |
| 1192 | #define DLT_MUX27010 236 |
| 1193 | |
| 1194 | /* |
| 1195 | * STANAG 5066 D_PDUs. Requested by M. Baris Demiray |
| 1196 | * <barisdemiray@gmail.com>. |
| 1197 | */ |
| 1198 | #define DLT_STANAG_5066_D_PDU 237 |
| 1199 | |
| 1200 | /* |
| 1201 | * Juniper-private data link type, as per request from |
| 1202 | * Hannes Gredler <hannes@juniper.net>. |
| 1203 | */ |
| 1204 | #define DLT_JUNIPER_ATM_CEMIC 238 |
| 1205 | |
| 1206 | /* |
| 1207 | * NetFilter LOG messages |
| 1208 | * (payload of netlink NFNL_SUBSYS_ULOG/NFULNL_MSG_PACKET packets) |
| 1209 | * |
| 1210 | * Requested by Jakub Zawadzki <darkjames-ws@darkjames.pl> |
| 1211 | */ |
| 1212 | #define DLT_NFLOG 239 |
| 1213 | |
| 1214 | /* |
| 1215 | * Hilscher Gesellschaft fuer Systemautomation mbH link-layer type |
| 1216 | * for Ethernet packets with a 4-byte pseudo-header and always |
| 1217 | * with the payload including the FCS, as supplied by their |
| 1218 | * netANALYZER hardware and software. |
| 1219 | * |
| 1220 | * Requested by Holger P. Frommer <HPfrommer@hilscher.com> |
| 1221 | */ |
| 1222 | #define DLT_NETANALYZER 240 |
| 1223 | |
| 1224 | /* |
| 1225 | * Hilscher Gesellschaft fuer Systemautomation mbH link-layer type |
| 1226 | * for Ethernet packets with a 4-byte pseudo-header and FCS and |
| 1227 | * with the Ethernet header preceded by 7 bytes of preamble and |
| 1228 | * 1 byte of SFD, as supplied by their netANALYZER hardware and |
| 1229 | * software. |
| 1230 | * |
| 1231 | * Requested by Holger P. Frommer <HPfrommer@hilscher.com> |
| 1232 | */ |
| 1233 | #define DLT_NETANALYZER_TRANSPARENT 241 |
| 1234 | |
| 1235 | /* |
| 1236 | * IP-over-InfiniBand, as specified by RFC 4391. |
| 1237 | * |
| 1238 | * Requested by Petr Sumbera <petr.sumbera@oracle.com>. |
| 1239 | */ |
| 1240 | #define DLT_IPOIB 242 |
| 1241 | |
| 1242 | /* |
| 1243 | * MPEG-2 transport stream (ISO 13818-1/ITU-T H.222.0). |
| 1244 | * |
| 1245 | * Requested by Guy Martin <gmsoft@tuxicoman.be>. |
| 1246 | */ |
| 1247 | #define DLT_MPEG_2_TS 243 |
| 1248 | |
| 1249 | /* |
| 1250 | * ng4T GmbH's UMTS Iub/Iur-over-ATM and Iub/Iur-over-IP format as |
| 1251 | * used by their ng40 protocol tester. |
| 1252 | * |
| 1253 | * Requested by Jens Grimmer <jens.grimmer@ng4t.com>. |
| 1254 | */ |
| 1255 | #define DLT_NG40 244 |
| 1256 | |
| 1257 | /* |
| 1258 | * Pseudo-header giving adapter number and flags, followed by an NFC |
| 1259 | * (Near-Field Communications) Logical Link Control Protocol (LLCP) PDU, |
| 1260 | * as specified by NFC Forum Logical Link Control Protocol Technical |
| 1261 | * Specification LLCP 1.1. |
| 1262 | * |
| 1263 | * Requested by Mike Wakerly <mikey@google.com>. |
| 1264 | */ |
| 1265 | #define DLT_NFC_LLCP 245 |
| 1266 | |
| 1267 | /* |
| 1268 | * 246 is used as LINKTYPE_PFSYNC; do not use it for any other purpose. |
| 1269 | * |
| 1270 | * DLT_PFSYNC has different values on different platforms, and all of |
| 1271 | * them collide with something used elsewhere. On platforms that |
| 1272 | * don't already define it, define it as 246. |
| 1273 | */ |
| 1274 | #if !defined(__FreeBSD__) && !defined(__OpenBSD__) && !defined(__NetBSD__) && !defined(__DragonFly__) && !defined(__APPLE__) |
| 1275 | #define DLT_PFSYNC 246 |
| 1276 | #endif |
| 1277 | |
| 1278 | /* |
| 1279 | * Raw InfiniBand packets, starting with the Local Routing Header. |
| 1280 | * |
| 1281 | * Requested by Oren Kladnitsky <orenk@mellanox.com>. |
| 1282 | */ |
| 1283 | #define DLT_INFINIBAND 247 |
| 1284 | |
| 1285 | /* |
| 1286 | * SCTP, with no lower-level protocols (i.e., no IPv4 or IPv6). |
| 1287 | * |
| 1288 | * Requested by Michael Tuexen <Michael.Tuexen@lurchi.franken.de>. |
| 1289 | */ |
| 1290 | #define DLT_SCTP 248 |
| 1291 | |
| 1292 | /* |
| 1293 | * USB packets, beginning with a USBPcap header. |
| 1294 | * |
| 1295 | * Requested by Tomasz Mon <desowin@gmail.com> |
| 1296 | */ |
| 1297 | #define DLT_USBPCAP 249 |
| 1298 | |
| 1299 | /* |
| 1300 | * Schweitzer Engineering Laboratories "RTAC" product serial-line |
| 1301 | * packets. |
| 1302 | * |
| 1303 | * Requested by Chris Bontje <chris_bontje@selinc.com>. |
| 1304 | */ |
| 1305 | #define DLT_RTAC_SERIAL 250 |
| 1306 | |
| 1307 | /* |
| 1308 | * Bluetooth Low Energy air interface link-layer packets. |
| 1309 | * |
| 1310 | * Requested by Mike Kershaw <dragorn@kismetwireless.net>. |
| 1311 | */ |
| 1312 | #define DLT_BLUETOOTH_LE_LL 251 |
| 1313 | |
| 1314 | /* |
| 1315 | * DLT type for upper-protocol layer PDU saves from Wireshark. |
| 1316 | * |
| 1317 | * the actual contents are determined by two TAGs, one or more of |
| 1318 | * which is stored with each packet: |
| 1319 | * |
| 1320 | * EXP_PDU_TAG_DISSECTOR_NAME the name of the Wireshark dissector |
| 1321 | * that can make sense of the data stored. |
| 1322 | * |
| 1323 | * EXP_PDU_TAG_HEUR_DISSECTOR_NAME the name of the Wireshark heuristic |
| 1324 | * dissector that can make sense of the |
| 1325 | * data stored. |
| 1326 | */ |
| 1327 | #define DLT_WIRESHARK_UPPER_PDU 252 |
| 1328 | |
| 1329 | /* |
| 1330 | * DLT type for the netlink protocol (nlmon devices). |
| 1331 | */ |
| 1332 | #define DLT_NETLINK 253 |
| 1333 | |
| 1334 | /* |
| 1335 | * Bluetooth Linux Monitor headers for the BlueZ stack. |
| 1336 | */ |
| 1337 | #define DLT_BLUETOOTH_LINUX_MONITOR 254 |
| 1338 | |
| 1339 | /* |
| 1340 | * Bluetooth Basic Rate/Enhanced Data Rate baseband packets, as |
| 1341 | * captured by Ubertooth. |
| 1342 | */ |
| 1343 | #define DLT_BLUETOOTH_BREDR_BB 255 |
| 1344 | |
| 1345 | /* |
| 1346 | * Bluetooth Low Energy link layer packets, as captured by Ubertooth. |
| 1347 | */ |
| 1348 | #define DLT_BLUETOOTH_LE_LL_WITH_PHDR 256 |
| 1349 | |
| 1350 | /* |
| 1351 | * PROFIBUS data link layer. |
| 1352 | */ |
| 1353 | #define DLT_PROFIBUS_DL 257 |
| 1354 | |
| 1355 | /* |
| 1356 | * Apple's DLT_PKTAP headers. |
| 1357 | * |
| 1358 | * Sadly, the folks at Apple either had no clue that the DLT_USERn values |
| 1359 | * are for internal use within an organization and partners only, and |
| 1360 | * didn't know that the right way to get a link-layer header type is to |
| 1361 | * ask tcpdump.org for one, or knew and didn't care, so they just |
| 1362 | * used DLT_USER2, which causes problems for everything except for |
| 1363 | * their version of tcpdump. |
| 1364 | * |
| 1365 | * So I'll just give them one; hopefully this will show up in a |
| 1366 | * libpcap release in time for them to get this into 10.10 Big Sur |
| 1367 | * or whatever Mavericks' successor is called. LINKTYPE_PKTAP |
| 1368 | * will be 258 *even on macOS*; that is *intentional*, so that |
| 1369 | * PKTAP files look the same on *all* OSes (different OSes can have |
| 1370 | * different numerical values for a given DLT_, but *MUST NOT* have |
| 1371 | * different values for what goes in a file, as files can be moved |
| 1372 | * between OSes!). |
| 1373 | * |
| 1374 | * When capturing, on a system with a Darwin-based OS, on a device |
| 1375 | * that returns 149 (DLT_USER2 and Apple's DLT_PKTAP) with this |
| 1376 | * version of libpcap, the DLT_ value for the pcap_t will be DLT_PKTAP, |
| 1377 | * and that will continue to be DLT_USER2 on Darwin-based OSes. That way, |
| 1378 | * binary compatibility with Mavericks is preserved for programs using |
| 1379 | * this version of libpcap. This does mean that if you were using |
| 1380 | * DLT_USER2 for some capture device on macOS, you can't do so with |
| 1381 | * this version of libpcap, just as you can't with Apple's libpcap - |
| 1382 | * on macOS, they define DLT_PKTAP to be DLT_USER2, so programs won't |
| 1383 | * be able to distinguish between PKTAP and whatever you were using |
| 1384 | * DLT_USER2 for. |
| 1385 | * |
| 1386 | * If the program saves the capture to a file using this version of |
| 1387 | * libpcap's pcap_dump code, the LINKTYPE_ value in the file will be |
| 1388 | * LINKTYPE_PKTAP, which will be 258, even on Darwin-based OSes. |
| 1389 | * That way, the file will *not* be a DLT_USER2 file. That means |
| 1390 | * that the latest version of tcpdump, when built with this version |
| 1391 | * of libpcap, and sufficiently recent versions of Wireshark will |
| 1392 | * be able to read those files and interpret them correctly; however, |
| 1393 | * Apple's version of tcpdump in OS X 10.9 won't be able to handle |
| 1394 | * them. (Hopefully, Apple will pick up this version of libpcap, |
| 1395 | * and the corresponding version of tcpdump, so that tcpdump will |
| 1396 | * be able to handle the old LINKTYPE_USER2 captures *and* the new |
| 1397 | * LINKTYPE_PKTAP captures.) |
| 1398 | */ |
| 1399 | #ifdef __APPLE__ |
| 1400 | #define DLT_PKTAP DLT_USER2 |
| 1401 | #else |
| 1402 | #define DLT_PKTAP 258 |
| 1403 | #endif |
| 1404 | |
| 1405 | /* |
| 1406 | * Ethernet packets preceded by a header giving the last 6 octets |
| 1407 | * of the preamble specified by 802.3-2012 Clause 65, section |
| 1408 | * 65.1.3.2 "Transmit". |
| 1409 | */ |
| 1410 | #define DLT_EPON 259 |
| 1411 | |
| 1412 | /* |
| 1413 | * IPMI trace packets, as specified by Table 3-20 "Trace Data Block Format" |
| 1414 | * in the PICMG HPM.2 specification. |
| 1415 | */ |
| 1416 | #define DLT_IPMI_HPM_2 260 |
| 1417 | |
| 1418 | /* |
| 1419 | * per Joshua Wright <jwright@hasborg.com>, formats for Zwave captures. |
| 1420 | */ |
| 1421 | #define DLT_ZWAVE_R1_R2 261 |
| 1422 | #define DLT_ZWAVE_R3 262 |
| 1423 | |
| 1424 | /* |
| 1425 | * per Steve Karg <skarg@users.sourceforge.net>, formats for Wattstopper |
| 1426 | * Digital Lighting Management room bus serial protocol captures. |
| 1427 | */ |
| 1428 | #define DLT_WATTSTOPPER_DLM 263 |
| 1429 | |
| 1430 | /* |
| 1431 | * ISO 14443 contactless smart card messages. |
| 1432 | */ |
| 1433 | #define DLT_ISO_14443 264 |
| 1434 | |
| 1435 | /* |
| 1436 | * Radio data system (RDS) groups. IEC 62106. |
| 1437 | * Per Jonathan Brucker <jonathan.brucke@gmail.com>. |
| 1438 | */ |
| 1439 | #define DLT_RDS 265 |
| 1440 | |
| 1441 | /* |
| 1442 | * USB packets, beginning with a Darwin (macOS, etc.) header. |
| 1443 | */ |
| 1444 | #define DLT_USB_DARWIN 266 |
| 1445 | |
| 1446 | /* |
| 1447 | * OpenBSD DLT_OPENFLOW. |
| 1448 | */ |
| 1449 | #define DLT_OPENFLOW 267 |
| 1450 | |
| 1451 | /* |
| 1452 | * SDLC frames containing SNA PDUs. |
| 1453 | */ |
| 1454 | #define DLT_SDLC 268 |
| 1455 | |
| 1456 | /* |
| 1457 | * per "Selvig, Bjorn" <b.selvig@ti.com> used for |
| 1458 | * TI protocol sniffer. |
| 1459 | */ |
| 1460 | #define DLT_TI_LLN_SNIFFER 269 |
| 1461 | |
| 1462 | /* |
| 1463 | * per: Erik de Jong <erikdejong at gmail.com> for |
| 1464 | * https://github.com/eriknl/LoRaTap/releases/tag/v0.1 |
| 1465 | */ |
| 1466 | #define DLT_LORATAP 270 |
| 1467 | |
| 1468 | /* |
| 1469 | * per: Stefanha at gmail.com for |
| 1470 | * https://lists.sandelman.ca/pipermail/tcpdump-workers/2017-May/000772.html |
| 1471 | * and: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/uapi/linux/vsockmon.h |
| 1472 | * for: https://qemu-project.org/Features/VirtioVsock |
| 1473 | */ |
| 1474 | #define DLT_VSOCK 271 |
| 1475 | |
| 1476 | /* |
| 1477 | * Nordic Semiconductor Bluetooth LE sniffer. |
| 1478 | */ |
| 1479 | #define DLT_NORDIC_BLE 272 |
| 1480 | |
| 1481 | /* |
| 1482 | * Excentis DOCSIS 3.1 RF sniffer (XRA-31) |
| 1483 | * per: bruno.verstuyft at excentis.com |
| 1484 | * https://www.xra31.com/xra-header |
| 1485 | */ |
| 1486 | #define DLT_DOCSIS31_XRA31 273 |
| 1487 | |
| 1488 | /* |
| 1489 | * mPackets, as specified by IEEE 802.3br Figure 99-4, starting |
| 1490 | * with the preamble and always ending with a CRC field. |
| 1491 | */ |
| 1492 | #define DLT_ETHERNET_MPACKET 274 |
| 1493 | |
| 1494 | /* |
| 1495 | * DisplayPort AUX channel monitoring data as specified by VESA |
| 1496 | * DisplayPort(DP) Standard preceded by a pseudo-header. |
| 1497 | * per dirk.eibach at gdsys.cc |
| 1498 | */ |
| 1499 | #define DLT_DISPLAYPORT_AUX 275 |
| 1500 | |
| 1501 | /* |
| 1502 | * Linux cooked sockets v2. |
| 1503 | */ |
| 1504 | #define DLT_LINUX_SLL2 276 |
| 1505 | |
| 1506 | /* |
| 1507 | * Sercos Monitor, per Manuel Jacob <manuel.jacob at steinbeis-stg.de> |
| 1508 | */ |
| 1509 | #define DLT_SERCOS_MONITOR 277 |
| 1510 | |
| 1511 | /* |
| 1512 | * OpenVizsla http://openvizsla.org is open source USB analyzer hardware. |
| 1513 | * It consists of FPGA with attached USB phy and FTDI chip for streaming |
| 1514 | * the data to the host PC. |
| 1515 | * |
| 1516 | * Current OpenVizsla data encapsulation format is described here: |
| 1517 | * https://github.com/matwey/libopenvizsla/wiki/OpenVizsla-protocol-description |
| 1518 | * |
| 1519 | */ |
| 1520 | #define DLT_OPENVIZSLA 278 |
| 1521 | |
| 1522 | /* |
| 1523 | * The Elektrobit High Speed Capture and Replay (EBHSCR) protocol is produced |
| 1524 | * by a PCIe Card for interfacing high speed automotive interfaces. |
| 1525 | * |
| 1526 | * The specification for this frame format can be found at: |
| 1527 | * https://www.elektrobit.com/ebhscr |
| 1528 | * |
| 1529 | * for Guenter.Ebermann at elektrobit.com |
| 1530 | * |
| 1531 | */ |
| 1532 | #define DLT_EBHSCR 279 |
| 1533 | |
| 1534 | /* |
| 1535 | * The https://fd.io vpp graph dispatch tracer produces pcap trace files |
| 1536 | * in the format documented here: |
| 1537 | * https://fdio-vpp.readthedocs.io/en/latest/gettingstarted/developers/vnet.html#graph-dispatcher-pcap-tracing |
| 1538 | */ |
| 1539 | #define DLT_VPP_DISPATCH 280 |
| 1540 | |
| 1541 | /* |
| 1542 | * Broadcom Ethernet switches (ROBO switch) 4 bytes proprietary tagging format. |
| 1543 | */ |
| 1544 | #define DLT_DSA_TAG_BRCM 281 |
| 1545 | #define DLT_DSA_TAG_BRCM_PREPEND 282 |
| 1546 | |
| 1547 | /* |
| 1548 | * IEEE 802.15.4 with pseudo-header and optional meta-data TLVs, PHY payload |
| 1549 | * exactly as it appears in the spec (no padding, no nothing), and FCS if |
| 1550 | * specified by FCS Type TLV; requested by James Ko <jck@exegin.com>. |
| 1551 | * Specification at https://github.com/jkcko/ieee802.15.4-tap |
| 1552 | */ |
| 1553 | #define DLT_IEEE802_15_4_TAP 283 |
| 1554 | |
| 1555 | /* |
| 1556 | * Marvell (Ethertype) Distributed Switch Architecture proprietary tagging format. |
| 1557 | */ |
| 1558 | #define DLT_DSA_TAG_DSA 284 |
| 1559 | #define DLT_DSA_TAG_EDSA 285 |
| 1560 | |
| 1561 | /* |
| 1562 | * Payload of lawful intercept packets using the ELEE protocol; |
| 1563 | * https://socket.hr/draft-dfranusic-opsawg-elee-00.xml |
| 1564 | * https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?url=https://socket.hr/draft-dfranusic-opsawg-elee-00.xml&modeAsFormat=html/ascii |
| 1565 | */ |
| 1566 | #define DLT_ELEE 286 |
| 1567 | |
| 1568 | /* |
| 1569 | * Serial frames transmitted between a host and a Z-Wave chip. |
| 1570 | */ |
| 1571 | #define DLT_Z_WAVE_SERIAL 287 |
| 1572 | |
| 1573 | /* |
| 1574 | * USB 2.0, 1.1, and 1.0 packets as transmitted over the cable. |
| 1575 | */ |
| 1576 | #define DLT_USB_2_0 288 |
| 1577 | |
| 1578 | /* |
| 1579 | * ATSC Link-Layer Protocol (A/330) packets. |
| 1580 | */ |
| 1581 | #define DLT_ATSC_ALP 289 |
| 1582 | |
| 1583 | /* |
| 1584 | * In case the code that includes this file (directly or indirectly) |
| 1585 | * has also included OS files that happen to define DLT_HIGH_MATCHING_MAX, |
| 1586 | * with a different value (perhaps because that OS hasn't picked up |
| 1587 | * the latest version of our DLT definitions), we undefine the |
| 1588 | * previous value of DLT_HIGH_MATCHING_MAX. |
| 1589 | */ |
| 1590 | #ifdef DLT_HIGH_MATCHING_MAX |
| 1591 | #undef DLT_HIGH_MATCHING_MAX |
| 1592 | #endif |
| 1593 | #define DLT_HIGH_MATCHING_MAX 289 /* highest value in the "matching" range */ |
| 1594 | |
| 1595 | /* |
| 1596 | * DLT and savefile link type values are split into a class and |
| 1597 | * a member of that class. A class value of 0 indicates a regular |
| 1598 | * DLT_/LINKTYPE_ value. |
| 1599 | */ |
| 1600 | #define DLT_CLASS(x) ((x) & 0x03ff0000) |
| 1601 | |
| 1602 | /* |
| 1603 | * NetBSD-specific generic "raw" link type. The class value indicates |
| 1604 | * that this is the generic raw type, and the lower 16 bits are the |
| 1605 | * address family we're dealing with. Those values are NetBSD-specific; |
| 1606 | * do not assume that they correspond to AF_ values for your operating |
| 1607 | * system. |
| 1608 | */ |
| 1609 | #define DLT_CLASS_NETBSD_RAWAF 0x02240000 |
| 1610 | #define DLT_NETBSD_RAWAF(af) (DLT_CLASS_NETBSD_RAWAF | (af)) |
| 1611 | #define DLT_NETBSD_RAWAF_AF(x) ((x) & 0x0000ffff) |
| 1612 | #define DLT_IS_NETBSD_RAWAF(x) (DLT_CLASS(x) == DLT_CLASS_NETBSD_RAWAF) |
| 1613 | |
| 1614 | #endif /* _NET_DLT_H_ */ |