Lines Matching +full:i2c +full:- +full:alias
1 /*-
39 * Link-layer header type codes.
42 * "tcpdump-workers@lists.tcpdump.org" for a value. Otherwise, you run
44 * purpose, and of having tools that read libpcap-format captures not
53 * for detailed descriptions of some of these link-layer header types.
67 #define DLT_ARCNET 7 /* ARCNET, with BSD-style header */
69 #define DLT_PPP 9 /* Point-to-point Protocol */
78 * XXX - DLT_ATM_RFC1483 is 13 in BSD/OS, and DLT_RAW is 14 in BSD/OS,
81 #define DLT_ATM_RFC1483 11 /* LLC-encapsulated ATM */
98 #define DLT_PPP_BSDOS 14 /* BSD/OS Point-to-point Protocol */
102 #define DLT_PPP_BSDOS 16 /* BSD/OS Point-to-point Protocol */
111 * a 1-byte ULP field (ULP-id)?
113 * a 1-byte flags field;
115 * a 2-byte "offsets" field;
117 * a 4-byte "D2 length" field (D2_Size?);
119 * a 4-byte "destination switch" field (or a 1-byte field
121 * sub fields, followed by a 3-byte Destination_Switch_Address
122 * field?, HIPPI-LE 3.4-style?);
124 * a 4-byte "source switch" field (or a 1-byte field containing the
126 * by a 3-byte Source_Switch_Address field, HIPPI-LE 3.4-style?);
128 * a 2-byte reserved field;
130 * a 6-byte destination address field;
132 * a 2-byte "local admin" field;
134 * a 6-byte source address field;
138 * This looks somewhat like something derived from the HIPPI-FP 4.4
139 * Header_Area, followed an HIPPI-FP 4.4 D1_Area containing a D1 data set
140 * with the header in HIPPI-LE 3.4 (ANSI X3.218-1993), followed by an
141 * HIPPI-FP 4.4 D2_Area (with no Offset) containing the 802.2 LLC header
151 * HIPPI is long-gone, and the source files found in an older version
153 * see a capture with this link-layer type.
170 * as 117 so that pflog captures would use a link-layer header type
189 * DLT_PFLOG, is not only OS-dependent but OS-version-dependent,
215 * The Axent Raptor firewall - now the Symantec Enterprise Firewall - uses
216 * a link-layer type of 99 for the tcpdump it supplies. The link-layer
225 * link-layer header type LINKTYPE_ values corresponding to DLT_ types
231 * Values starting with 104 are used for newly-assigned link-layer
232 * header type values; for those link-layer header types, the DLT_
244 * it with a different value should define it here with that value -
265 * so that we don't have to worry about the link-layer header.)
278 * that the AF_ type in the link-layer header is in network byte order.
303 * as link-layer types corresponding to DLT_ types that might differ
344 * Registered for Cisco-internal use.
349 * For 802.11 cards using the Prism II chips, with a link-layer
356 * Reserved for Aironet 802.11 cards, with an Aironet link-layer header
364 * 121 was reserved for Siemens HiPath HDLC on 2002-01-25, as
367 * On 2004-02-25, a FreeBSD checkin to sys/net/bpf.h was made that
369 * does DLT_ <-> LINKTYPE_ mapping, mapping DLT_PFSYNC to a
371 * dump files with 246 as the link-layer header type. (Earlier
373 * have written them out with a link-layer header type of 121.)
376 * its libpcap does no DLT_ <-> LINKTYPE_ mapping, so it would
377 * write out DLT_PFSYNC dump files with use 18 as the link-layer
381 * current versions, their libpcaps do DLT_ <-> LINKTYPE_ mapping,
383 * should write out DLT_PFSYNC dump files with 246 as the link-layer
386 * them out with a link-layer header type of 18.)
404 * Code that uses pcap_datalink() to determine the link-layer header
411 * FreeBSD's libpcap won't map a link-layer header type of 18 - i.e.,
413 * DragonFly BSD, and macOS - to DLT_PFSYNC, so code built with FreeBSD's
416 * Other libpcaps won't map a link-layer header type of 121 to DLT_PFSYNC;
428 * This is for RFC 2625 IP-over-Fibre Channel.
430 * This is not for use with raw Fibre Channel, where the link-layer
431 * header starts with a Fibre Channel frame header; it's for IP-over-FC,
432 * where the link-layer header starts with an RFC 2625 Network_Header
439 * pseudo-header followed by an AALn PDU.
442 * with different pseudo-headers.
444 * If ATM software returns a pseudo-header with VPI/VCI information
446 * LANE, LLC-multiplexed traffic, etc.), it should not use
449 * pseudo-header and the form of the pseudo-header.
462 * Header for 802.11 plus a number of bits of link-layer information
472 * which includes a means to include meta-information
483 * Linux's ARCNET headers, however, have a 2-byte offset field
492 * Juniper-private data link types, as per request from
494 * for passing on chassis-internal metainformation such as
507 * Apple IP-over-IEEE 1394, as per a request from Dieter Siegmund
508 * <dieter@apple.com>. The header that's presented is an Ethernet-like
527 #define DLT_MTP2_WITH_PHDR 139 /* pseudo-header with various info, followed by MTP2 */
528 #define DLT_MTP2 140 /* MTP2, without pseudo-header */
529 #define DLT_MTP3 141 /* MTP3, without pseudo-header or MTP2 */
530 #define DLT_SCCP 142 /* SCCP, without pseudo-header or MTP2 or MTP3 */
538 * Linux-IrDA packets. Protocol defined at https://www.irda.org.
542 * This is exactly the format you would get capturing on a Linux-IrDA
544 * Note the capture is done in "Linux-cooked" mode, so each packet include
561 * Reserved for private use. If you have some link-layer header type
563 * using that link-layer header type not ever be sent outside your
570 * your private versions of capture-file-reading tools to read; in
582 * Instead, ask "tcpdump-workers@lists.tcpdump.org" for a new DLT_ value,
603 * For future use with 802.11 captures - defined by AbsoluteValue
604 * Systems to store a number of bits of link-layer information
609 * but it might be used by some non-AVS drivers now or in the
615 * Juniper-private data link type, as per request from
617 * for passing on chassis-internal metainformation such as
632 * supply pppd with outgoing packets so it can do dial-on-demand and
633 * hangup-on-lack-of-demand; incoming packets are filtered out so they
639 * the direction - 0x00 = IN, 0x01 = OUT.
651 * Juniper-private data link type, as per request from
653 * for passing on chassis-internal metainformation such as
660 #define DLT_GPF_T 170 /* GPF-T (ITU-T G.7041/Y.1303) */
661 #define DLT_GPF_F 171 /* GPF-F (ITU-T G.7041/Y.1303) */
671 * Juniper-private data link type, as per request from
681 * the link-layer header.
684 #define DLT_ERF_POS 176 /* Packet-over-SONET */
688 * for vISDN (http://www.orlandi.com/visdn/). Its link-layer header
695 * Juniper-private data link type, as per request from
697 * The DLT_ are used for prepending meta-information
699 * before standard Ethernet, PPP, Frelay & C-HDLC Frames
712 * Juniper-private data link type, as per request from
731 * Please refer to the A653-1 standard for more information.
739 * However, that header didn't work all that well - it left out some
740 * useful information - and was abandoned in favor of the DLT_USB_LINUX
746 * For source-code compatibility, we also define DLT_USB to have this
778 * http://www.can-cia.org/downloads/?269
801 * Juniper-private data link type, as per request from
814 * We keep the name DLT_IEEE802_15_4 as an alias for backwards
822 * Various link-layer types, with a pseudo-header, for SITA
828 * Various link-layer types, with a pseudo-header, for Endace DAG cards;
842 * IPMB packet for IPMI, beginning with a 2-byte header, followed by
843 * the I2C slave address, followed by the netFn and LUN, etc..
846 * XXX - this used to be called DLT_IPMB, back when we got the
848 * had no extra 2-byte header. We've renamed it; if anybody used
849 * DLT_IPMB and assumed no 2-byte header, this will cause the compile
858 * Juniper-private data link type, as per request from
865 * Bluetooth HCI UART transport layer (part H:4), with pseudo-header
871 * AX.25 packet with a 1-byte KISS header; see
875 * as per Richard Stearn <richard@rns-stearn.demon.co.uk>.
881 * with no pseudo-header.
887 * PPP, with a one-byte direction pseudo-header prepended - zero means
888 * "received by this host", non-zero (any non-zero value) means "sent by
889 * this host" - as per Will Barker <w.barker@zen.co.uk>.
897 * Cisco HDLC, with a one-byte direction pseudo-header prepended - zero
898 * means "received by this host", non-zero (any non-zero value) means
899 * "sent by this host" - as per Will Barker <w.barker@zen.co.uk>.
904 * Frame Relay, with a one-byte direction pseudo-header prepended - zero
905 * means "received by this host" (DCE -> DTE), non-zero (any non-zero
906 * value) means "sent by this host" (DTE -> DCE) - as per Will Barker
912 * LAPB, with a one-byte direction pseudo-header prepended - zero means
913 * "received by this host" (DCE -> DTE), non-zero (any non-zero value)
914 * means "sent by this host" (DTE -> DCE)- as per Will Barker
920 * 208 is reserved for an as-yet-unspecified proprietary link-layer
925 * IPMB with a Linux-specific pseudo-header; as requested by Alexey Neyman
931 * FlexRay automotive bus - http://www.flexray.com/ - as requested
938 * transport - https://www.mostcooperation.com/ - as requested
944 * Local Interconnect Network (LIN) bus for vehicle networks -
945 * http://www.lin-subbus.org/ - as requested by Hannes Kaelber
951 * X2E-private data link type used for serial line capture,
957 * X2E-private data link type used for the Xoraya data logger
964 * nothing), but with the PHY-level data for non-ASK PHYs (4 octets
966 * reserved bit, and then the MAC-layer data, starting with the
990 * MPLS, with an MPLS label as the link-layer header.
998 * padded to 64 bytes; required for memory-mapped access.
1003 * DECT packets, with a pseudo-header; requested by
1009 * From: "Lidwa, Eric (GSFC-582.0)[SGT INC]" <eric.lidwa-1@nasa.gov>
1010 * Date: Mon, 11 May 2009 11:18:30 -0500
1029 * Fibre Channel FC-2 frames, beginning with a Frame_Header.
1035 * Fibre Channel FC-2 frames, beginning with an encoding of the
1038 * The encodings represent the frame delimiters as 4-byte sequences
1041 * byte values; for example, SOFi2, which is K28.5 - D21.5 - D1.2 - D21.2,
1049 * Solaris ipnet pseudo-header; requested by Darren Reed <Darren.Reed@Sun.COM>.
1051 * The pseudo-header starts with a one-byte version number; for version 2,
1052 * the pseudo-header is:
1065 * dli_version is 2 for the current version of the pseudo-header.
1070 * dli_htype is a "hook type" - 0 for incoming packets, 1 for outgoing
1074 * dli_pktlen is the length of the packet data following the pseudo-header
1076 * pseudo-header, assuming the entire pseudo-header was captured).
1091 * An IPv4 or IPv6 datagram follows the pseudo-header; dli_family indicates
1097 * CAN (Controller Area Network) frames, with a pseudo-header as supplied
1098 * by Linux SocketCAN, and with multi-byte numerical fields in that header
1099 * in big-endian byte order.
1122 * Raw D-Bus:
1128 * https://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-messages
1133 * https://dbus.freedesktop.org/doc/dbus-specification.html#auth-protocol
1140 * Juniper-private data link type, as per request from
1148 * DVB-CI (DVB Common Interface for communication between a PC Card
1151 * https://www.kaiser.cx/pcap-dvbci.html
1161 * *not* the same as, 27.010). Requested by Hans-Christoph Schemmel
1162 * <hans-christoph.schemmel@cinterion.com>.
1173 * Juniper-private data link type, as per request from
1182 * Requested by Jakub Zawadzki <darkjames-ws@darkjames.pl>
1187 * Hilscher Gesellschaft fuer Systemautomation mbH link-layer type
1188 * for Ethernet packets with a 4-byte pseudo-header and always
1197 * Hilscher Gesellschaft fuer Systemautomation mbH link-layer type
1198 * for Ethernet packets with a 4-byte pseudo-header and FCS and
1208 * IP-over-InfiniBand, as specified by RFC 4391.
1215 * MPEG-2 transport stream (ISO 13818-1/ITU-T H.222.0).
1222 * ng4T GmbH's UMTS Iub/Iur-over-ATM and Iub/Iur-over-IP format as
1230 * Pseudo-header giving adapter number and flags, followed by an NFC
1231 * (Near-Field Communications) Logical Link Control Protocol (LLCP) PDU,
1258 * SCTP, with no lower-level protocols (i.e., no IPv4 or IPv6).
1272 * Schweitzer Engineering Laboratories "RTAC" product serial-line
1280 * Bluetooth Low Energy air interface link-layer packets.
1287 * DLT type for upper-protocol layer PDU saves from Wireshark.
1332 * didn't know that the right way to get a link-layer header type is to
1346 * When capturing, on a system with a Darwin-based OS, on a device
1349 * and that will continue to be DLT_USER2 on Darwin-based OSes. That way,
1353 * this version of libpcap, just as you can't with Apple's libpcap -
1360 * LINKTYPE_PKTAP, which will be 258, even on Darwin-based OSes.
1379 * of the preamble specified by 802.3-2012 Clause 65, section
1385 * IPMI trace packets, as specified by Table 3-20 "Trace Data Block Format"
1442 * https://lists.sandelman.ca/pipermail/tcpdump-workers/2017-May/000772.html
1444 * for: https://qemu-project.org/Features/VirtioVsock
1454 * Excentis DOCSIS 3.1 RF sniffer (XRA-31)
1456 * https://www.xra31.com/xra-header
1461 * mPackets, as specified by IEEE 802.3br Figure 99-4, starting
1468 * DisplayPort(DP) Standard preceded by a pseudo-header.
1479 * Sercos Monitor, per Manuel Jacob <manuel.jacob at steinbeis-stg.de>
1489 * https://github.com/matwey/libopenvizsla/wiki/OpenVizsla-protocol-description
1509 …* https://fdio-vpp.readthedocs.io/en/latest/gettingstarted/developers/vnet.html#graph-dispatcher-p…
1520 * IEEE 802.15.4 with pseudo-header and optional meta-data TLVs, PHY payload
1523 * Specification at https://github.com/jkcko/ieee802.15.4-tap
1535 * https://socket.hr/draft-dfranusic-opsawg-elee-00.xml
1536 …* https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?url=https://socket.hr/draft-dfranusic-opsawg-…
1541 * Serial frames transmitted between a host and a Z-Wave chip.
1551 * ATSC Link-Layer Protocol (A/330) packets.
1575 * NetBSD-specific generic "raw" link type. The class value indicates
1577 * address family we're dealing with. Those values are NetBSD-specific;