Lines Matching +full:ipmi +full:- +full:ipmb
1 /*-
41 * Link-layer header type codes.
44 * "tcpdump-workers@lists.tcpdump.org" for a value. Otherwise, you run
46 * purpose, and of having tools that read libpcap-format captures not
55 * for detailed descriptions of some of these link-layer header types.
74 #define DLT_ARCNET 7 /* ARCNET, with BSD-style header */
76 #define DLT_PPP 9 /* Point-to-point Protocol */
88 * a free-for-all. Perhaps 11 is DLT_ATM_RFC1483 everywhere 11
104 * XXX - DLT_ATM_RFC1483 is 13 in BSD/OS, and DLT_RAW is 14 in BSD/OS,
109 #define DLT_ATM_RFC1483 11 /* LLC-encapsulated ATM */
126 #define DLT_PPP_BSDOS 14 /* BSD/OS Point-to-point Protocol */
130 #define DLT_PPP_BSDOS 16 /* BSD/OS Point-to-point Protocol */
139 * a 1-byte ULP field (ULP-id)?
141 * a 1-byte flags field;
143 * a 2-byte "offsets" field;
145 * a 4-byte "D2 length" field (D2_Size?);
147 * a 4-byte "destination switch" field (or a 1-byte field
149 * sub fields, followed by a 3-byte Destination_Switch_Address
150 * field?, HIPPI-LE 3.4-style?);
152 * a 4-byte "source switch" field (or a 1-byte field containing the
154 * by a 3-byte Source_Switch_Address field, HIPPI-LE 3.4-style?);
156 * a 2-byte reserved field;
158 * a 6-byte destination address field;
160 * a 2-byte "local admin" field;
162 * a 6-byte source address field;
166 * This looks somewhat like something derived from the HIPPI-FP 4.4
167 * Header_Area, followed an HIPPI-FP 4.4 D1_Area containing a D1 data set
168 * with the header in HIPPI-LE 3.4 (ANSI X3.218-1993), followed by an
169 * HIPPI-FP 4.4 D2_Area (with no Offset) containing the 802.2 LLC header
179 * HIPPI is long-gone, and the source files found in an older version
181 * see a capture with this link-layer type.
198 * as 117 so that pflog captures would use a link-layer header type
241 * The Axent Raptor firewall - now the Symantec Enterprise Firewall - uses
242 * a link-layer type of 99 for the tcpdump it supplies. The link-layer
251 * link-layer header type LINKTYPE_ values corresponding to DLT_ types
257 * Values starting with 104 are used for newly-assigned link-layer
258 * header type values; for those link-layer header types, the DLT_
270 * it with a different value should define it here with that value -
291 * so that we don't have to worry about the link-layer header.)
304 * that the AF_ type in the link-layer header is in network byte order.
329 * as link-layer types corresponding to DLT_ types that might differ
370 * Registered for Cisco-internal use.
375 * For 802.11 cards using the Prism II chips, with a link-layer
382 * Reserved for Aironet 802.11 cards, with an Aironet link-layer header
390 * 121 was reserved for Siemens HiPath HDLC on 2002-01-25, as
393 * On 2004-02-25, a FreeBSD checkin to sys/net/bpf.h was made that
395 * does DLT_ <-> LINKTYPE_ mapping, mapping DLT_PFSYNC to a
397 * dump files with 246 as the link-layer header type. (Earlier
399 * have written them out with a link-layer header type of 121.)
402 * its libpcap does no DLT_ <-> LINKTYPE_ mapping, so it would
403 * write out DLT_PFSYNC dump files with use 18 as the link-layer
407 * current versions, their libpcaps do DLT_ <-> LINKTYPE_ mapping,
409 * should write out DLT_PFSYNC dump files with 246 as the link-layer
412 * them out with a link-layer header type of 18.)
430 * Code that uses pcap_datalink() to determine the link-layer header
437 * FreeBSD's libpcap won't map a link-layer header type of 18 - i.e.,
439 * DragonFly BSD, and macOS - to DLT_PFSYNC, so code built with FreeBSD's
442 * Other libpcaps won't map a link-layer header type of 121 to DLT_PFSYNC;
454 * This is for RFC 2625 IP-over-Fibre Channel.
456 * This is not for use with raw Fibre Channel, where the link-layer
457 * header starts with a Fibre Channel frame header; it's for IP-over-FC,
458 * where the link-layer header starts with an RFC 2625 Network_Header
465 * pseudo-header followed by an AALn PDU.
468 * with different pseudo-headers.
470 * If ATM software returns a pseudo-header with VPI/VCI information
472 * LANE, LLC-multiplexed traffic, etc.), it should not use
475 * pseudo-header and the form of the pseudo-header.
488 * Header for 802.11 plus a number of bits of link-layer information
498 * which includes a means to include meta-information
509 * Linux's ARCNET headers, however, have a 2-byte offset field
518 * Juniper-private data link types, as per request from
520 * for passing on chassis-internal metainformation such as
533 * Apple IP-over-IEEE 1394, as per a request from Dieter Siegmund
534 * <dieter@apple.com>. The header that's presented is an Ethernet-like
553 #define DLT_MTP2_WITH_PHDR 139 /* pseudo-header with various info, followed by MTP2 */
554 #define DLT_MTP2 140 /* MTP2, without pseudo-header */
555 #define DLT_MTP3 141 /* MTP3, without pseudo-header or MTP2 */
556 #define DLT_SCCP 142 /* SCCP, without pseudo-header or MTP2 or MTP3 */
564 * Linux-IrDA packets. Protocol defined at https://www.irda.org.
568 * This is exactly the format you would get capturing on a Linux-IrDA
570 * Note the capture is done in "Linux-cooked" mode, so each packet include
587 * Reserved for private use. If you have some link-layer header type
589 * using that link-layer header type not ever be sent outside your
596 * your private versions of capture-file-reading tools to read; in
608 * Instead, ask "tcpdump-workers@lists.tcpdump.org" for a new DLT_ value,
629 * For future use with 802.11 captures - defined by AbsoluteValue
630 * Systems to store a number of bits of link-layer information
635 * but it might be used by some non-AVS drivers now or in the
641 * Juniper-private data link type, as per request from
643 * for passing on chassis-internal metainformation such as
658 * supply pppd with outgoing packets so it can do dial-on-demand and
659 * hangup-on-lack-of-demand; incoming packets are filtered out so they
665 * the direction - 0x00 = IN, 0x01 = OUT.
677 * Juniper-private data link type, as per request from
679 * for passing on chassis-internal metainformation such as
686 #define DLT_GPF_T 170 /* GPF-T (ITU-T G.7041/Y.1303) */
687 #define DLT_GPF_F 171 /* GPF-F (ITU-T G.7041/Y.1303) */
697 * Juniper-private data link type, as per request from
707 * the link-layer header.
710 #define DLT_ERF_POS 176 /* Packet-over-SONET */
714 * for vISDN (http://www.orlandi.com/visdn/). Its link-layer header
721 * Juniper-private data link type, as per request from
723 * The DLT_ are used for prepending meta-information
725 * before standard Ethernet, PPP, Frelay & C-HDLC Frames
738 * Juniper-private data link type, as per request from
757 * Please refer to the A653-1 standard for more information.
765 * However, that header didn't work all that well - it left out some
766 * useful information - and was abandoned in favor of the DLT_USB_LINUX
772 * For source-code compatibility, we also define DLT_USB to have this
804 * http://www.can-cia.org/downloads/?269
827 * Juniper-private data link type, as per request from
848 * Various link-layer types, with a pseudo-header, for SITA
854 * Various link-layer types, with a pseudo-header, for Endace DAG cards;
868 * IPMB packet for IPMI, beginning with a 2-byte header, followed by
872 * XXX - this used to be called DLT_IPMB, back when we got the
874 * had no extra 2-byte header. We've renamed it; if anybody used
875 * DLT_IPMB and assumed no 2-byte header, this will cause the compile
884 * Juniper-private data link type, as per request from
891 * Bluetooth HCI UART transport layer (part H:4), with pseudo-header
897 * AX.25 packet with a 1-byte KISS header; see
901 * as per Richard Stearn <richard@rns-stearn.demon.co.uk>.
907 * with no pseudo-header.
913 * PPP, with a one-byte direction pseudo-header prepended - zero means
914 * "received by this host", non-zero (any non-zero value) means "sent by
915 * this host" - as per Will Barker <w.barker@zen.co.uk>.
923 * Cisco HDLC, with a one-byte direction pseudo-header prepended - zero
924 * means "received by this host", non-zero (any non-zero value) means
925 * "sent by this host" - as per Will Barker <w.barker@zen.co.uk>.
930 * Frame Relay, with a one-byte direction pseudo-header prepended - zero
931 * means "received by this host" (DCE -> DTE), non-zero (any non-zero
932 * value) means "sent by this host" (DTE -> DCE) - as per Will Barker
938 * LAPB, with a one-byte direction pseudo-header prepended - zero means
939 * "received by this host" (DCE -> DTE), non-zero (any non-zero value)
940 * means "sent by this host" (DTE -> DCE)- as per Will Barker
946 * 208 is reserved for an as-yet-unspecified proprietary link-layer
951 * IPMB with a Linux-specific pseudo-header; as requested by Alexey Neyman
957 * FlexRay automotive bus - http://www.flexray.com/ - as requested
964 * transport - https://www.mostcooperation.com/ - as requested
970 * Local Interconnect Network (LIN) bus for vehicle networks -
971 * http://www.lin-subbus.org/ - as requested by Hannes Kaelber
977 * X2E-private data link type used for serial line capture,
983 * X2E-private data link type used for the Xoraya data logger
990 * nothing), but with the PHY-level data for non-ASK PHYs (4 octets
992 * reserved bit, and then the MAC-layer data, starting with the
1016 * MPLS, with an MPLS label as the link-layer header.
1024 * padded to 64 bytes; required for memory-mapped access.
1029 * DECT packets, with a pseudo-header; requested by
1035 * From: "Lidwa, Eric (GSFC-582.0)[SGT INC]" <eric.lidwa-1@nasa.gov>
1036 * Date: Mon, 11 May 2009 11:18:30 -0500
1055 * Fibre Channel FC-2 frames, beginning with a Frame_Header.
1061 * Fibre Channel FC-2 frames, beginning with an encoding of the
1064 * The encodings represent the frame delimiters as 4-byte sequences
1067 * byte values; for example, SOFi2, which is K28.5 - D21.5 - D1.2 - D21.2,
1075 * Solaris ipnet pseudo-header; requested by Darren Reed <Darren.Reed@Sun.COM>.
1077 * The pseudo-header starts with a one-byte version number; for version 2,
1078 * the pseudo-header is:
1091 * dli_version is 2 for the current version of the pseudo-header.
1096 * dli_htype is a "hook type" - 0 for incoming packets, 1 for outgoing
1100 * dli_pktlen is the length of the packet data following the pseudo-header
1102 * pseudo-header, assuming the entire pseudo-header was captured).
1117 * An IPv4 or IPv6 datagram follows the pseudo-header; dli_family indicates
1123 * CAN (Controller Area Network) frames, with a pseudo-header as supplied
1124 * by Linux SocketCAN, and with multi-byte numerical fields in that header
1125 * in big-endian byte order.
1148 * Raw D-Bus:
1154 * https://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-messages
1159 * https://dbus.freedesktop.org/doc/dbus-specification.html#auth-protocol
1166 * Juniper-private data link type, as per request from
1174 * DVB-CI (DVB Common Interface for communication between a PC Card
1177 * https://www.kaiser.cx/pcap-dvbci.html
1187 * *not* the same as, 27.010). Requested by Hans-Christoph Schemmel
1188 * <hans-christoph.schemmel@cinterion.com>.
1199 * Juniper-private data link type, as per request from
1208 * Requested by Jakub Zawadzki <darkjames-ws@darkjames.pl>
1213 * Hilscher Gesellschaft fuer Systemautomation mbH link-layer type
1214 * for Ethernet packets with a 4-byte pseudo-header and always
1223 * Hilscher Gesellschaft fuer Systemautomation mbH link-layer type
1224 * for Ethernet packets with a 4-byte pseudo-header and FCS and
1234 * IP-over-InfiniBand, as specified by RFC 4391.
1241 * MPEG-2 transport stream (ISO 13818-1/ITU-T H.222.0).
1248 * ng4T GmbH's UMTS Iub/Iur-over-ATM and Iub/Iur-over-IP format as
1256 * Pseudo-header giving adapter number and flags, followed by an NFC
1257 * (Near-Field Communications) Logical Link Control Protocol (LLCP) PDU,
1284 * SCTP, with no lower-level protocols (i.e., no IPv4 or IPv6).
1298 * Schweitzer Engineering Laboratories "RTAC" product serial-line
1306 * Bluetooth Low Energy air interface link-layer packets.
1313 * DLT type for upper-protocol layer PDU saves from Wireshark.
1358 * didn't know that the right way to get a link-layer header type is to
1372 * When capturing, on a system with a Darwin-based OS, on a device
1375 * and that will continue to be DLT_USER2 on Darwin-based OSes. That way,
1379 * this version of libpcap, just as you can't with Apple's libpcap -
1386 * LINKTYPE_PKTAP, which will be 258, even on Darwin-based OSes.
1405 * of the preamble specified by 802.3-2012 Clause 65, section
1411 * IPMI trace packets, as specified by Table 3-20 "Trace Data Block Format"
1468 * https://lists.sandelman.ca/pipermail/tcpdump-workers/2017-May/000772.html
1470 * for: https://qemu-project.org/Features/VirtioVsock
1480 * Excentis DOCSIS 3.1 RF sniffer (XRA-31)
1482 * https://www.xra31.com/xra-header
1487 * mPackets, as specified by IEEE 802.3br Figure 99-4, starting
1494 * DisplayPort(DP) Standard preceded by a pseudo-header.
1505 * Sercos Monitor, per Manuel Jacob <manuel.jacob at steinbeis-stg.de>
1515 * https://github.com/matwey/libopenvizsla/wiki/OpenVizsla-protocol-description
1535 …* https://fdio-vpp.readthedocs.io/en/latest/gettingstarted/developers/vnet.html#graph-dispatcher-p…
1546 * IEEE 802.15.4 with pseudo-header and optional meta-data TLVs, PHY payload
1549 * Specification at https://github.com/jkcko/ieee802.15.4-tap
1561 * https://socket.hr/draft-dfranusic-opsawg-elee-00.xml
1562 …* https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?url=https://socket.hr/draft-dfranusic-opsawg-…
1567 * Serial frames transmitted between a host and a Z-Wave chip.
1577 * ATSC Link-Layer Protocol (A/330) packets.