📄 pcap-bpf.h
字号:
/* * For 802.11 cards using the Prism II chips, with a link-layer * header including Prism monitor mode information plus an 802.11 * header. */#define DLT_PRISM_HEADER 119/* * Reserved for Aironet 802.11 cards, with an Aironet link-layer header * (see Doug Ambrisko's FreeBSD patches). */#define DLT_AIRONET_HEADER 120/* * Reserved for Siemens HiPath HDLC. */#define DLT_HHDLC 121/* * This is for RFC 2625 IP-over-Fibre Channel. * * This is not for use with raw Fibre Channel, where the link-layer * header starts with a Fibre Channel frame header; it's for IP-over-FC, * where the link-layer header starts with an RFC 2625 Network_Header * field. */#define DLT_IP_OVER_FC 122/* * This is for Full Frontal ATM on Solaris with SunATM, with a * pseudo-header followed by an AALn PDU. * * There may be other forms of Full Frontal ATM on other OSes, * with different pseudo-headers. * * If ATM software returns a pseudo-header with VPI/VCI information * (and, ideally, packet type information, e.g. signalling, ILMI, * LANE, LLC-multiplexed traffic, etc.), it should not use * DLT_ATM_RFC1483, but should get a new DLT_ value, so tcpdump * and the like don't have to infer the presence or absence of a * pseudo-header and the form of the pseudo-header. */#define DLT_SUNATM 123 /* Solaris+SunATM *//* * Reserved as per request from Kent Dahlgren <kent@praesum.com> * for private use. */#define DLT_RIO 124 /* RapidIO */#define DLT_PCI_EXP 125 /* PCI Express */#define DLT_AURORA 126 /* Xilinx Aurora link layer *//* * BSD header for 802.11 plus a number of bits of link-layer information * including radio information. */#define DLT_IEEE802_11_RADIO 127 /* 802.11 plus BSD radio header *//* * Reserved for the TZSP encapsulation, as per request from * Chris Waters <chris.waters@networkchemistry.com> * TZSP is a generic encapsulation for any other link type, * which includes a means to include meta-information * with the packet, e.g. signal strength and channel * for 802.11 packets. */#define DLT_TZSP 128 /* Tazmen Sniffer Protocol *//* * BSD's ARCNET headers have the source host, destination host, * and type at the beginning of the packet; that's what's handed * up to userland via BPF. * * Linux's ARCNET headers, however, have a 2-byte offset field * between the host IDs and the type; that's what's handed up * to userland via PF_PACKET sockets. * * We therefore have to have separate DLT_ values for them. */#define DLT_ARCNET_LINUX 129 /* ARCNET *//* * Juniper-private data link types, as per request from * Hannes Gredler <hannes@juniper.net>. The DLT_s are used * for passing on chassis-internal metainformation such as * QOS profiles, etc.. */#define DLT_JUNIPER_MLPPP 130#define DLT_JUNIPER_MLFR 131#define DLT_JUNIPER_ES 132#define DLT_JUNIPER_GGSN 133#define DLT_JUNIPER_MFR 134#define DLT_JUNIPER_ATM2 135#define DLT_JUNIPER_SERVICES 136#define DLT_JUNIPER_ATM1 137/* * Apple IP-over-IEEE 1394, as per a request from Dieter Siegmund * <dieter@apple.com>. The header that's presented is an Ethernet-like * header: * * #define FIREWIRE_EUI64_LEN 8 * struct firewire_header { * u_char firewire_dhost[FIREWIRE_EUI64_LEN]; * u_char firewire_shost[FIREWIRE_EUI64_LEN]; * u_short firewire_type; * }; * * with "firewire_type" being an Ethernet type value, rather than, * for example, raw GASP frames being handed up. */#define DLT_APPLE_IP_OVER_IEEE1394 138/* * 139 through 142 are reserved for SS7. *//* * Reserved for DOCSIS MAC frames. */#define DLT_DOCSIS 143/* * Linux-IrDA packets. Protocol defined at http://www.irda.org. * Those packets include IrLAP headers and above (IrLMP...), but * don't include Phy framing (SOF/EOF/CRC & byte stuffing), because Phy * framing can be handled by the hardware and depend on the bitrate. * This is exactly the format you would get capturing on a Linux-IrDA * interface (irdaX), but not on a raw serial port. * Note the capture is done in "Linux-cooked" mode, so each packet include * a fake packet header (struct sll_header). This is because IrDA packet * decoding is dependant on the direction of the packet (incomming or * outgoing). * When/if other platform implement IrDA capture, we may revisit the * issue and define a real DLT_IRDA... * Jean II */#define DLT_LINUX_IRDA 144/* * Reserved for IBM SP switch and IBM Next Federation switch. */#define DLT_IBM_SP 145#define DLT_IBM_SN 146/* * Reserved for private use. If you have some link-layer header type * that you want to use within your organization, with the capture files * using that link-layer header type not ever be sent outside your * organization, you can use these values. * * No libpcap release will use these for any purpose, nor will any * tcpdump release use them, either. * * Do *NOT* use these in capture files that you expect anybody not using * your private versions of capture-file-reading tools to read; in * particular, do *NOT* use them in products, otherwise you may find that * people won't be able to use tcpdump, or snort, or Ethereal, or... to * read capture files from your firewall/intrusion detection/traffic * monitoring/etc. appliance, or whatever product uses that DLT_ value, * and you may also find that the developers of those applications will * not accept patches to let them read those files. * * Also, do not use them if somebody might send you a capture using them * for *their* private type and tools using them for *your* private type * would have to read them. * * Instead, ask "tcpdump-workers@tcpdump.org" for a new DLT_ value, * as per the comment above, and use the type you're given. */#define DLT_USER0 147#define DLT_USER1 148#define DLT_USER2 149#define DLT_USER3 150#define DLT_USER4 151#define DLT_USER5 152#define DLT_USER6 153#define DLT_USER7 154#define DLT_USER8 155#define DLT_USER9 156#define DLT_USER10 157#define DLT_USER11 158#define DLT_USER12 159#define DLT_USER13 160#define DLT_USER14 161#define DLT_USER15 162/* * For future use with 802.11 captures - defined by AbsoluteValue * Systems to store a number of bits of link-layer information * including radio information: * * http://www.shaftnet.org/~pizza/software/capturefrm.txt * * but could and arguably should also be used by non-AVS Linux * 802.11 drivers; that may happen in the future. */#define DLT_IEEE802_11_RADIO_AVS 163 /* 802.11 plus AVS radio header *//* * Juniper-private data link type, as per request from * Hannes Gredler <hannes@juniper.net>. The DLT_s are used * for passing on chassis-internal metainformation such as * QOS profiles, etc.. */#define DLT_JUNIPER_MONITOR 164/* * The instruction encodings. *//* instruction classes */#define BPF_CLASS(code) ((code) & 0x07)#define BPF_LD 0x00#define BPF_LDX 0x01#define BPF_ST 0x02#define BPF_STX 0x03#define BPF_ALU 0x04#define BPF_JMP 0x05#define BPF_RET 0x06#define BPF_MISC 0x07/* ld/ldx fields */#define BPF_SIZE(code) ((code) & 0x18)#define BPF_W 0x00#define BPF_H 0x08#define BPF_B 0x10#define BPF_MODE(code) ((code) & 0xe0)#define BPF_IMM 0x00#define BPF_ABS 0x20#define BPF_IND 0x40#define BPF_MEM 0x60#define BPF_LEN 0x80#define BPF_MSH 0xa0/* alu/jmp fields */#define BPF_OP(code) ((code) & 0xf0)#define BPF_ADD 0x00#define BPF_SUB 0x10#define BPF_MUL 0x20#define BPF_DIV 0x30#define BPF_OR 0x40#define BPF_AND 0x50#define BPF_LSH 0x60#define BPF_RSH 0x70#define BPF_NEG 0x80#define BPF_JA 0x00#define BPF_JEQ 0x10#define BPF_JGT 0x20#define BPF_JGE 0x30#define BPF_JSET 0x40#define BPF_SRC(code) ((code) & 0x08)#define BPF_K 0x00#define BPF_X 0x08/* ret - BPF_K and BPF_X also apply */#define BPF_RVAL(code) ((code) & 0x18)#define BPF_A 0x10/* misc */#define BPF_MISCOP(code) ((code) & 0xf8)#define BPF_TAX 0x00#define BPF_TXA 0x80/* * The instruction data structure. */struct bpf_insn { u_short code; u_char jt; u_char jf; bpf_int32 k;};/* * Macros for insn array initializers. */#define BPF_STMT(code, k) { (u_short)(code), 0, 0, k }#define BPF_JUMP(code, k, jt, jf) { (u_short)(code), jt, jf, k }#if __STDC__ || defined(__cplusplus)extern int bpf_validate(struct bpf_insn *, int);extern u_int bpf_filter(struct bpf_insn *, u_char *, u_int, u_int);#elseextern int bpf_validate();extern u_int bpf_filter();#endif/* * Number of scratch memory words (for BPF_LD|BPF_MEM and BPF_ST). */#define BPF_MEMWORDS 16#ifdef __cplusplus}#endif#endif
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -