2005-01-07 01:45:51 +00:00
|
|
|
/*-
|
1994-05-24 10:09:53 +00:00
|
|
|
* Copyright (c) 1990, 1991, 1993
|
2011-12-31 07:21:28 +00:00
|
|
|
* The Regents of the University of California. All rights reserved.
|
1994-05-24 10:09:53 +00:00
|
|
|
*
|
|
|
|
* This code is derived from the Stanford/CMU enet packet filter,
|
|
|
|
* (net/enet.c) distributed as part of 4.3BSD, and code contributed
|
|
|
|
* to Berkeley by Steven McCanne and Van Jacobson both of Lawrence
|
|
|
|
* Berkeley Laboratory.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
* 4. Neither the name of the University nor the names of its contributors
|
|
|
|
* may be used to endorse or promote products derived from this software
|
|
|
|
* without specific prior written permission.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
* SUCH DAMAGE.
|
|
|
|
*
|
|
|
|
* @(#)bpf.h 8.1 (Berkeley) 6/10/93
|
1996-08-19 20:28:25 +00:00
|
|
|
* @(#)bpf.h 1.34 (LBL) 6/16/96
|
1994-05-24 10:09:53 +00:00
|
|
|
*
|
1999-08-28 01:08:13 +00:00
|
|
|
* $FreeBSD$
|
1994-05-24 10:09:53 +00:00
|
|
|
*/
|
|
|
|
|
1994-08-21 05:11:48 +00:00
|
|
|
#ifndef _NET_BPF_H_
|
|
|
|
#define _NET_BPF_H_
|
|
|
|
|
1996-08-19 20:28:25 +00:00
|
|
|
/* BSD style release date */
|
|
|
|
#define BPF_RELEASE 199606
|
|
|
|
|
|
|
|
typedef int32_t bpf_int32;
|
|
|
|
typedef u_int32_t bpf_u_int32;
|
Implement flexible BPF timestamping framework.
- Allow setting format, resolution and accuracy of BPF time stamps per
listener. Previously, we were only able to use microtime(9). Now we can
set various resolutions and accuracies with ioctl(2) BIOCSTSTAMP command.
Similarly, we can get the current resolution and accuracy with BIOCGTSTAMP
command. Document all supported options in bpf(4) and their uses.
- Introduce new time stamp 'struct bpf_ts' and header 'struct bpf_xhdr'.
The new time stamp has both 64-bit second and fractional parts. bpf_xhdr
has this time stamp instead of 'struct timeval' for bh_tstamp. The new
structures let us use bh_tstamp of same size on both 32-bit and 64-bit
platforms without adding additional shims for 32-bit binaries. On 64-bit
platforms, size of BPF header does not change compared to bpf_hdr as its
members are already all 64-bit long. On 32-bit platforms, the size may
increase by 8 bytes. For backward compatibility, struct bpf_hdr with
struct timeval is still the default header unless new time stamp format is
explicitly requested. However, the behaviour may change in the future and
all relevant code is wrapped around "#ifdef BURN_BRIDGES" for now.
- Add experimental support for tagging mbufs with time stamps from a lower
layer, e.g., device driver. Currently, mbuf_tags(9) is used to tag mbufs.
The time stamps must be uptime in 'struct bintime' format as binuptime(9)
and getbinuptime(9) do.
Reviewed by: net@
2010-06-15 19:28:44 +00:00
|
|
|
typedef int64_t bpf_int64;
|
|
|
|
typedef u_int64_t bpf_u_int64;
|
1996-08-19 20:28:25 +00:00
|
|
|
|
1994-05-24 10:09:53 +00:00
|
|
|
/*
|
1995-05-30 08:16:23 +00:00
|
|
|
* Alignment macros. BPF_WORDALIGN rounds up to the next
|
|
|
|
* even multiple of BPF_ALIGNMENT.
|
1994-05-24 10:09:53 +00:00
|
|
|
*/
|
1998-10-04 21:53:59 +00:00
|
|
|
#define BPF_ALIGNMENT sizeof(long)
|
1994-05-24 10:09:53 +00:00
|
|
|
#define BPF_WORDALIGN(x) (((x)+(BPF_ALIGNMENT-1))&~(BPF_ALIGNMENT-1))
|
|
|
|
|
|
|
|
#define BPF_MAXINSNS 512
|
2000-01-15 19:46:12 +00:00
|
|
|
#define BPF_MAXBUFSIZE 0x80000
|
1994-05-24 10:09:53 +00:00
|
|
|
#define BPF_MINBUFSIZE 32
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Structure for BIOCSETF.
|
|
|
|
*/
|
|
|
|
struct bpf_program {
|
|
|
|
u_int bf_len;
|
|
|
|
struct bpf_insn *bf_insns;
|
|
|
|
};
|
1995-05-30 08:16:23 +00:00
|
|
|
|
1994-05-24 10:09:53 +00:00
|
|
|
/*
|
|
|
|
* Struct returned by BIOCGSTATS.
|
|
|
|
*/
|
|
|
|
struct bpf_stat {
|
|
|
|
u_int bs_recv; /* number of packets received */
|
|
|
|
u_int bs_drop; /* number of packets dropped */
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
1995-05-30 08:16:23 +00:00
|
|
|
* Struct return by BIOCVERSION. This represents the version number of
|
1994-05-24 10:09:53 +00:00
|
|
|
* the filter language described by the instruction encodings below.
|
|
|
|
* bpf understands a program iff kernel_major == filter_major &&
|
|
|
|
* kernel_minor >= filter_minor, that is, if the value returned by the
|
|
|
|
* running kernel has the same major number and a minor number equal
|
|
|
|
* equal to or less than the filter being downloaded. Otherwise, the
|
|
|
|
* results are undefined, meaning an error may be returned or packets
|
|
|
|
* may be accepted haphazardly.
|
|
|
|
* It has nothing to do with the source code version.
|
|
|
|
*/
|
|
|
|
struct bpf_version {
|
|
|
|
u_short bv_major;
|
|
|
|
u_short bv_minor;
|
|
|
|
};
|
1996-08-19 20:28:25 +00:00
|
|
|
/* Current version number of filter architecture. */
|
1994-05-24 10:09:53 +00:00
|
|
|
#define BPF_MAJOR_VERSION 1
|
|
|
|
#define BPF_MINOR_VERSION 1
|
|
|
|
|
Introduce support for zero-copy BPF buffering, which reduces the
overhead of packet capture by allowing a user process to directly "loan"
buffer memory to the kernel rather than using read(2) to explicitly copy
data from kernel address space.
The user process will issue new BPF ioctls to set the shared memory
buffer mode and provide pointers to buffers and their size. The kernel
then wires and maps the pages into kernel address space using sf_buf(9),
which on supporting architectures will use the direct map region. The
current "buffered" access mode remains the default, and support for
zero-copy buffers must, for the time being, be explicitly enabled using
a sysctl for the kernel to accept requests to use it.
The kernel and user process synchronize use of the buffers with atomic
operations, avoiding the need for system calls under load; the user
process may use select()/poll()/kqueue() to manage blocking while
waiting for network data if the user process is able to consume data
faster than the kernel generates it. Patchs to libpcap are available
to allow libpcap applications to transparently take advantage of this
support. Detailed information on the new API may be found in bpf(4),
including specific atomic operations and memory barriers required to
synchronize buffer use safely.
These changes modify the base BPF implementation to (roughly) abstrac
the current buffer model, allowing the new shared memory model to be
added, and add new monitoring statistics for netstat to print. The
implementation, with the exception of some monitoring hanges that break
the netstat monitoring ABI for BPF, will be MFC'd.
Zerocopy bpf buffers are still considered experimental are disabled
by default. To experiment with this new facility, adjust the
net.bpf.zerocopy_enable sysctl variable to 1.
Changes to libpcap will be made available as a patch for the time being,
and further refinements to the implementation are expected.
Sponsored by: Seccuris Inc.
In collaboration with: rwatson
Tested by: pwood, gallatin
MFC after: 4 months [1]
[1] Certain portions will probably not be MFCed, specifically things
that can break the monitoring ABI.
2008-03-24 13:49:17 +00:00
|
|
|
/*
|
|
|
|
* Historically, BPF has supported a single buffering model, first using mbuf
|
|
|
|
* clusters in kernel, and later using malloc(9) buffers in kernel. We now
|
|
|
|
* support multiple buffering modes, which may be queried and set using
|
|
|
|
* BIOCGETBUFMODE and BIOCSETBUFMODE. So as to avoid handling the complexity
|
|
|
|
* of changing modes while sniffing packets, the mode becomes fixed once an
|
|
|
|
* interface has been attached to the BPF descriptor.
|
|
|
|
*/
|
|
|
|
#define BPF_BUFMODE_BUFFER 1 /* Kernel buffers with read(). */
|
|
|
|
#define BPF_BUFMODE_ZBUF 2 /* Zero-copy buffers. */
|
|
|
|
|
|
|
|
/*-
|
|
|
|
* Struct used by BIOCSETZBUF, BIOCROTZBUF: describes up to two zero-copy
|
|
|
|
* buffer as used by BPF.
|
|
|
|
*/
|
|
|
|
struct bpf_zbuf {
|
|
|
|
void *bz_bufa; /* Location of 'a' zero-copy buffer. */
|
|
|
|
void *bz_bufb; /* Location of 'b' zero-copy buffer. */
|
|
|
|
size_t bz_buflen; /* Size of zero-copy buffers. */
|
|
|
|
};
|
|
|
|
|
Implement flexible BPF timestamping framework.
- Allow setting format, resolution and accuracy of BPF time stamps per
listener. Previously, we were only able to use microtime(9). Now we can
set various resolutions and accuracies with ioctl(2) BIOCSTSTAMP command.
Similarly, we can get the current resolution and accuracy with BIOCGTSTAMP
command. Document all supported options in bpf(4) and their uses.
- Introduce new time stamp 'struct bpf_ts' and header 'struct bpf_xhdr'.
The new time stamp has both 64-bit second and fractional parts. bpf_xhdr
has this time stamp instead of 'struct timeval' for bh_tstamp. The new
structures let us use bh_tstamp of same size on both 32-bit and 64-bit
platforms without adding additional shims for 32-bit binaries. On 64-bit
platforms, size of BPF header does not change compared to bpf_hdr as its
members are already all 64-bit long. On 32-bit platforms, the size may
increase by 8 bytes. For backward compatibility, struct bpf_hdr with
struct timeval is still the default header unless new time stamp format is
explicitly requested. However, the behaviour may change in the future and
all relevant code is wrapped around "#ifdef BURN_BRIDGES" for now.
- Add experimental support for tagging mbufs with time stamps from a lower
layer, e.g., device driver. Currently, mbuf_tags(9) is used to tag mbufs.
The time stamps must be uptime in 'struct bintime' format as binuptime(9)
and getbinuptime(9) do.
Reviewed by: net@
2010-06-15 19:28:44 +00:00
|
|
|
#define BIOCGBLEN _IOR('B', 102, u_int)
|
|
|
|
#define BIOCSBLEN _IOWR('B', 102, u_int)
|
|
|
|
#define BIOCSETF _IOW('B', 103, struct bpf_program)
|
|
|
|
#define BIOCFLUSH _IO('B', 104)
|
|
|
|
#define BIOCPROMISC _IO('B', 105)
|
|
|
|
#define BIOCGDLT _IOR('B', 106, u_int)
|
|
|
|
#define BIOCGETIF _IOR('B', 107, struct ifreq)
|
|
|
|
#define BIOCSETIF _IOW('B', 108, struct ifreq)
|
|
|
|
#define BIOCSRTIMEOUT _IOW('B', 109, struct timeval)
|
|
|
|
#define BIOCGRTIMEOUT _IOR('B', 110, struct timeval)
|
|
|
|
#define BIOCGSTATS _IOR('B', 111, struct bpf_stat)
|
|
|
|
#define BIOCIMMEDIATE _IOW('B', 112, u_int)
|
|
|
|
#define BIOCVERSION _IOR('B', 113, struct bpf_version)
|
|
|
|
#define BIOCGRSIG _IOR('B', 114, u_int)
|
|
|
|
#define BIOCSRSIG _IOW('B', 115, u_int)
|
|
|
|
#define BIOCGHDRCMPLT _IOR('B', 116, u_int)
|
|
|
|
#define BIOCSHDRCMPLT _IOW('B', 117, u_int)
|
|
|
|
#define BIOCGDIRECTION _IOR('B', 118, u_int)
|
|
|
|
#define BIOCSDIRECTION _IOW('B', 119, u_int)
|
|
|
|
#define BIOCSDLT _IOW('B', 120, u_int)
|
|
|
|
#define BIOCGDLTLIST _IOWR('B', 121, struct bpf_dltlist)
|
2005-08-22 19:35:48 +00:00
|
|
|
#define BIOCLOCK _IO('B', 122)
|
Implement flexible BPF timestamping framework.
- Allow setting format, resolution and accuracy of BPF time stamps per
listener. Previously, we were only able to use microtime(9). Now we can
set various resolutions and accuracies with ioctl(2) BIOCSTSTAMP command.
Similarly, we can get the current resolution and accuracy with BIOCGTSTAMP
command. Document all supported options in bpf(4) and their uses.
- Introduce new time stamp 'struct bpf_ts' and header 'struct bpf_xhdr'.
The new time stamp has both 64-bit second and fractional parts. bpf_xhdr
has this time stamp instead of 'struct timeval' for bh_tstamp. The new
structures let us use bh_tstamp of same size on both 32-bit and 64-bit
platforms without adding additional shims for 32-bit binaries. On 64-bit
platforms, size of BPF header does not change compared to bpf_hdr as its
members are already all 64-bit long. On 32-bit platforms, the size may
increase by 8 bytes. For backward compatibility, struct bpf_hdr with
struct timeval is still the default header unless new time stamp format is
explicitly requested. However, the behaviour may change in the future and
all relevant code is wrapped around "#ifdef BURN_BRIDGES" for now.
- Add experimental support for tagging mbufs with time stamps from a lower
layer, e.g., device driver. Currently, mbuf_tags(9) is used to tag mbufs.
The time stamps must be uptime in 'struct bintime' format as binuptime(9)
and getbinuptime(9) do.
Reviewed by: net@
2010-06-15 19:28:44 +00:00
|
|
|
#define BIOCSETWF _IOW('B', 123, struct bpf_program)
|
|
|
|
#define BIOCFEEDBACK _IOW('B', 124, u_int)
|
|
|
|
#define BIOCGETBUFMODE _IOR('B', 125, u_int)
|
|
|
|
#define BIOCSETBUFMODE _IOW('B', 126, u_int)
|
|
|
|
#define BIOCGETZMAX _IOR('B', 127, size_t)
|
|
|
|
#define BIOCROTZBUF _IOR('B', 128, struct bpf_zbuf)
|
|
|
|
#define BIOCSETZBUF _IOW('B', 129, struct bpf_zbuf)
|
|
|
|
#define BIOCSETFNR _IOW('B', 130, struct bpf_program)
|
|
|
|
#define BIOCGTSTAMP _IOR('B', 131, u_int)
|
|
|
|
#define BIOCSTSTAMP _IOW('B', 132, u_int)
|
2007-02-26 22:24:14 +00:00
|
|
|
|
|
|
|
/* Obsolete */
|
|
|
|
#define BIOCGSEESENT BIOCGDIRECTION
|
|
|
|
#define BIOCSSEESENT BIOCSDIRECTION
|
|
|
|
|
|
|
|
/* Packet directions */
|
|
|
|
enum bpf_direction {
|
|
|
|
BPF_D_IN, /* See incoming packets */
|
|
|
|
BPF_D_INOUT, /* See incoming and outgoing packets */
|
|
|
|
BPF_D_OUT /* See outgoing packets */
|
|
|
|
};
|
1994-05-24 10:09:53 +00:00
|
|
|
|
Implement flexible BPF timestamping framework.
- Allow setting format, resolution and accuracy of BPF time stamps per
listener. Previously, we were only able to use microtime(9). Now we can
set various resolutions and accuracies with ioctl(2) BIOCSTSTAMP command.
Similarly, we can get the current resolution and accuracy with BIOCGTSTAMP
command. Document all supported options in bpf(4) and their uses.
- Introduce new time stamp 'struct bpf_ts' and header 'struct bpf_xhdr'.
The new time stamp has both 64-bit second and fractional parts. bpf_xhdr
has this time stamp instead of 'struct timeval' for bh_tstamp. The new
structures let us use bh_tstamp of same size on both 32-bit and 64-bit
platforms without adding additional shims for 32-bit binaries. On 64-bit
platforms, size of BPF header does not change compared to bpf_hdr as its
members are already all 64-bit long. On 32-bit platforms, the size may
increase by 8 bytes. For backward compatibility, struct bpf_hdr with
struct timeval is still the default header unless new time stamp format is
explicitly requested. However, the behaviour may change in the future and
all relevant code is wrapped around "#ifdef BURN_BRIDGES" for now.
- Add experimental support for tagging mbufs with time stamps from a lower
layer, e.g., device driver. Currently, mbuf_tags(9) is used to tag mbufs.
The time stamps must be uptime in 'struct bintime' format as binuptime(9)
and getbinuptime(9) do.
Reviewed by: net@
2010-06-15 19:28:44 +00:00
|
|
|
/* Time stamping functions */
|
|
|
|
#define BPF_T_MICROTIME 0x0000
|
|
|
|
#define BPF_T_NANOTIME 0x0001
|
|
|
|
#define BPF_T_BINTIME 0x0002
|
|
|
|
#define BPF_T_NONE 0x0003
|
|
|
|
#define BPF_T_FORMAT_MASK 0x0003
|
|
|
|
#define BPF_T_NORMAL 0x0000
|
2011-12-31 07:21:28 +00:00
|
|
|
#define BPF_T_FAST 0x0100
|
|
|
|
#define BPF_T_MONOTONIC 0x0200
|
|
|
|
#define BPF_T_MONOTONIC_FAST (BPF_T_FAST | BPF_T_MONOTONIC)
|
|
|
|
#define BPF_T_FLAG_MASK 0x0300
|
Implement flexible BPF timestamping framework.
- Allow setting format, resolution and accuracy of BPF time stamps per
listener. Previously, we were only able to use microtime(9). Now we can
set various resolutions and accuracies with ioctl(2) BIOCSTSTAMP command.
Similarly, we can get the current resolution and accuracy with BIOCGTSTAMP
command. Document all supported options in bpf(4) and their uses.
- Introduce new time stamp 'struct bpf_ts' and header 'struct bpf_xhdr'.
The new time stamp has both 64-bit second and fractional parts. bpf_xhdr
has this time stamp instead of 'struct timeval' for bh_tstamp. The new
structures let us use bh_tstamp of same size on both 32-bit and 64-bit
platforms without adding additional shims for 32-bit binaries. On 64-bit
platforms, size of BPF header does not change compared to bpf_hdr as its
members are already all 64-bit long. On 32-bit platforms, the size may
increase by 8 bytes. For backward compatibility, struct bpf_hdr with
struct timeval is still the default header unless new time stamp format is
explicitly requested. However, the behaviour may change in the future and
all relevant code is wrapped around "#ifdef BURN_BRIDGES" for now.
- Add experimental support for tagging mbufs with time stamps from a lower
layer, e.g., device driver. Currently, mbuf_tags(9) is used to tag mbufs.
The time stamps must be uptime in 'struct bintime' format as binuptime(9)
and getbinuptime(9) do.
Reviewed by: net@
2010-06-15 19:28:44 +00:00
|
|
|
#define BPF_T_FORMAT(t) ((t) & BPF_T_FORMAT_MASK)
|
|
|
|
#define BPF_T_FLAG(t) ((t) & BPF_T_FLAG_MASK)
|
|
|
|
#define BPF_T_VALID(t) \
|
|
|
|
((t) == BPF_T_NONE || (BPF_T_FORMAT(t) != BPF_T_NONE && \
|
|
|
|
((t) & ~(BPF_T_FORMAT_MASK | BPF_T_FLAG_MASK)) == 0))
|
|
|
|
|
2011-12-31 07:21:28 +00:00
|
|
|
#define BPF_T_MICROTIME_FAST (BPF_T_MICROTIME | BPF_T_FAST)
|
|
|
|
#define BPF_T_NANOTIME_FAST (BPF_T_NANOTIME | BPF_T_FAST)
|
|
|
|
#define BPF_T_BINTIME_FAST (BPF_T_BINTIME | BPF_T_FAST)
|
Implement flexible BPF timestamping framework.
- Allow setting format, resolution and accuracy of BPF time stamps per
listener. Previously, we were only able to use microtime(9). Now we can
set various resolutions and accuracies with ioctl(2) BIOCSTSTAMP command.
Similarly, we can get the current resolution and accuracy with BIOCGTSTAMP
command. Document all supported options in bpf(4) and their uses.
- Introduce new time stamp 'struct bpf_ts' and header 'struct bpf_xhdr'.
The new time stamp has both 64-bit second and fractional parts. bpf_xhdr
has this time stamp instead of 'struct timeval' for bh_tstamp. The new
structures let us use bh_tstamp of same size on both 32-bit and 64-bit
platforms without adding additional shims for 32-bit binaries. On 64-bit
platforms, size of BPF header does not change compared to bpf_hdr as its
members are already all 64-bit long. On 32-bit platforms, the size may
increase by 8 bytes. For backward compatibility, struct bpf_hdr with
struct timeval is still the default header unless new time stamp format is
explicitly requested. However, the behaviour may change in the future and
all relevant code is wrapped around "#ifdef BURN_BRIDGES" for now.
- Add experimental support for tagging mbufs with time stamps from a lower
layer, e.g., device driver. Currently, mbuf_tags(9) is used to tag mbufs.
The time stamps must be uptime in 'struct bintime' format as binuptime(9)
and getbinuptime(9) do.
Reviewed by: net@
2010-06-15 19:28:44 +00:00
|
|
|
#define BPF_T_MICROTIME_MONOTONIC (BPF_T_MICROTIME | BPF_T_MONOTONIC)
|
|
|
|
#define BPF_T_NANOTIME_MONOTONIC (BPF_T_NANOTIME | BPF_T_MONOTONIC)
|
|
|
|
#define BPF_T_BINTIME_MONOTONIC (BPF_T_BINTIME | BPF_T_MONOTONIC)
|
2011-12-31 07:21:28 +00:00
|
|
|
#define BPF_T_MICROTIME_MONOTONIC_FAST (BPF_T_MICROTIME | BPF_T_MONOTONIC_FAST)
|
|
|
|
#define BPF_T_NANOTIME_MONOTONIC_FAST (BPF_T_NANOTIME | BPF_T_MONOTONIC_FAST)
|
|
|
|
#define BPF_T_BINTIME_MONOTONIC_FAST (BPF_T_BINTIME | BPF_T_MONOTONIC_FAST)
|
Implement flexible BPF timestamping framework.
- Allow setting format, resolution and accuracy of BPF time stamps per
listener. Previously, we were only able to use microtime(9). Now we can
set various resolutions and accuracies with ioctl(2) BIOCSTSTAMP command.
Similarly, we can get the current resolution and accuracy with BIOCGTSTAMP
command. Document all supported options in bpf(4) and their uses.
- Introduce new time stamp 'struct bpf_ts' and header 'struct bpf_xhdr'.
The new time stamp has both 64-bit second and fractional parts. bpf_xhdr
has this time stamp instead of 'struct timeval' for bh_tstamp. The new
structures let us use bh_tstamp of same size on both 32-bit and 64-bit
platforms without adding additional shims for 32-bit binaries. On 64-bit
platforms, size of BPF header does not change compared to bpf_hdr as its
members are already all 64-bit long. On 32-bit platforms, the size may
increase by 8 bytes. For backward compatibility, struct bpf_hdr with
struct timeval is still the default header unless new time stamp format is
explicitly requested. However, the behaviour may change in the future and
all relevant code is wrapped around "#ifdef BURN_BRIDGES" for now.
- Add experimental support for tagging mbufs with time stamps from a lower
layer, e.g., device driver. Currently, mbuf_tags(9) is used to tag mbufs.
The time stamps must be uptime in 'struct bintime' format as binuptime(9)
and getbinuptime(9) do.
Reviewed by: net@
2010-06-15 19:28:44 +00:00
|
|
|
|
1994-05-24 10:09:53 +00:00
|
|
|
/*
|
|
|
|
* Structure prepended to each packet.
|
|
|
|
*/
|
Implement flexible BPF timestamping framework.
- Allow setting format, resolution and accuracy of BPF time stamps per
listener. Previously, we were only able to use microtime(9). Now we can
set various resolutions and accuracies with ioctl(2) BIOCSTSTAMP command.
Similarly, we can get the current resolution and accuracy with BIOCGTSTAMP
command. Document all supported options in bpf(4) and their uses.
- Introduce new time stamp 'struct bpf_ts' and header 'struct bpf_xhdr'.
The new time stamp has both 64-bit second and fractional parts. bpf_xhdr
has this time stamp instead of 'struct timeval' for bh_tstamp. The new
structures let us use bh_tstamp of same size on both 32-bit and 64-bit
platforms without adding additional shims for 32-bit binaries. On 64-bit
platforms, size of BPF header does not change compared to bpf_hdr as its
members are already all 64-bit long. On 32-bit platforms, the size may
increase by 8 bytes. For backward compatibility, struct bpf_hdr with
struct timeval is still the default header unless new time stamp format is
explicitly requested. However, the behaviour may change in the future and
all relevant code is wrapped around "#ifdef BURN_BRIDGES" for now.
- Add experimental support for tagging mbufs with time stamps from a lower
layer, e.g., device driver. Currently, mbuf_tags(9) is used to tag mbufs.
The time stamps must be uptime in 'struct bintime' format as binuptime(9)
and getbinuptime(9) do.
Reviewed by: net@
2010-06-15 19:28:44 +00:00
|
|
|
struct bpf_ts {
|
|
|
|
bpf_int64 bt_sec; /* seconds */
|
|
|
|
bpf_u_int64 bt_frac; /* fraction */
|
|
|
|
};
|
|
|
|
struct bpf_xhdr {
|
|
|
|
struct bpf_ts bh_tstamp; /* time stamp */
|
|
|
|
bpf_u_int32 bh_caplen; /* length of captured portion */
|
|
|
|
bpf_u_int32 bh_datalen; /* original length of packet */
|
|
|
|
u_short bh_hdrlen; /* length of bpf header (this struct
|
|
|
|
plus alignment padding) */
|
|
|
|
};
|
|
|
|
/* Obsolete */
|
1994-05-24 10:09:53 +00:00
|
|
|
struct bpf_hdr {
|
|
|
|
struct timeval bh_tstamp; /* time stamp */
|
1996-08-19 20:28:25 +00:00
|
|
|
bpf_u_int32 bh_caplen; /* length of captured portion */
|
|
|
|
bpf_u_int32 bh_datalen; /* original length of packet */
|
1994-05-24 10:09:53 +00:00
|
|
|
u_short bh_hdrlen; /* length of bpf header (this struct
|
|
|
|
plus alignment padding) */
|
|
|
|
};
|
1999-12-29 04:46:21 +00:00
|
|
|
#ifdef _KERNEL
|
Implement flexible BPF timestamping framework.
- Allow setting format, resolution and accuracy of BPF time stamps per
listener. Previously, we were only able to use microtime(9). Now we can
set various resolutions and accuracies with ioctl(2) BIOCSTSTAMP command.
Similarly, we can get the current resolution and accuracy with BIOCGTSTAMP
command. Document all supported options in bpf(4) and their uses.
- Introduce new time stamp 'struct bpf_ts' and header 'struct bpf_xhdr'.
The new time stamp has both 64-bit second and fractional parts. bpf_xhdr
has this time stamp instead of 'struct timeval' for bh_tstamp. The new
structures let us use bh_tstamp of same size on both 32-bit and 64-bit
platforms without adding additional shims for 32-bit binaries. On 64-bit
platforms, size of BPF header does not change compared to bpf_hdr as its
members are already all 64-bit long. On 32-bit platforms, the size may
increase by 8 bytes. For backward compatibility, struct bpf_hdr with
struct timeval is still the default header unless new time stamp format is
explicitly requested. However, the behaviour may change in the future and
all relevant code is wrapped around "#ifdef BURN_BRIDGES" for now.
- Add experimental support for tagging mbufs with time stamps from a lower
layer, e.g., device driver. Currently, mbuf_tags(9) is used to tag mbufs.
The time stamps must be uptime in 'struct bintime' format as binuptime(9)
and getbinuptime(9) do.
Reviewed by: net@
2010-06-15 19:28:44 +00:00
|
|
|
#define MTAG_BPF 0x627066
|
|
|
|
#define MTAG_BPF_TIMESTAMP 0
|
1994-05-24 10:09:53 +00:00
|
|
|
#endif
|
|
|
|
|
Introduce support for zero-copy BPF buffering, which reduces the
overhead of packet capture by allowing a user process to directly "loan"
buffer memory to the kernel rather than using read(2) to explicitly copy
data from kernel address space.
The user process will issue new BPF ioctls to set the shared memory
buffer mode and provide pointers to buffers and their size. The kernel
then wires and maps the pages into kernel address space using sf_buf(9),
which on supporting architectures will use the direct map region. The
current "buffered" access mode remains the default, and support for
zero-copy buffers must, for the time being, be explicitly enabled using
a sysctl for the kernel to accept requests to use it.
The kernel and user process synchronize use of the buffers with atomic
operations, avoiding the need for system calls under load; the user
process may use select()/poll()/kqueue() to manage blocking while
waiting for network data if the user process is able to consume data
faster than the kernel generates it. Patchs to libpcap are available
to allow libpcap applications to transparently take advantage of this
support. Detailed information on the new API may be found in bpf(4),
including specific atomic operations and memory barriers required to
synchronize buffer use safely.
These changes modify the base BPF implementation to (roughly) abstrac
the current buffer model, allowing the new shared memory model to be
added, and add new monitoring statistics for netstat to print. The
implementation, with the exception of some monitoring hanges that break
the netstat monitoring ABI for BPF, will be MFC'd.
Zerocopy bpf buffers are still considered experimental are disabled
by default. To experiment with this new facility, adjust the
net.bpf.zerocopy_enable sysctl variable to 1.
Changes to libpcap will be made available as a patch for the time being,
and further refinements to the implementation are expected.
Sponsored by: Seccuris Inc.
In collaboration with: rwatson
Tested by: pwood, gallatin
MFC after: 4 months [1]
[1] Certain portions will probably not be MFCed, specifically things
that can break the monitoring ABI.
2008-03-24 13:49:17 +00:00
|
|
|
/*
|
|
|
|
* When using zero-copy BPF buffers, a shared memory header is present
|
|
|
|
* allowing the kernel BPF implementation and user process to synchronize
|
|
|
|
* without using system calls. This structure defines that header. When
|
|
|
|
* accessing these fields, appropriate atomic operation and memory barriers
|
|
|
|
* are required in order not to see stale or out-of-order data; see bpf(4)
|
|
|
|
* for reference code to access these fields from userspace.
|
|
|
|
*
|
|
|
|
* The layout of this structure is critical, and must not be changed; if must
|
|
|
|
* fit in a single page on all architectures.
|
|
|
|
*/
|
|
|
|
struct bpf_zbuf_header {
|
|
|
|
volatile u_int bzh_kernel_gen; /* Kernel generation number. */
|
|
|
|
volatile u_int bzh_kernel_len; /* Length of data in the buffer. */
|
|
|
|
volatile u_int bzh_user_gen; /* User generation number. */
|
|
|
|
u_int _bzh_pad[5];
|
|
|
|
};
|
|
|
|
|
1994-05-24 10:09:53 +00:00
|
|
|
/*
|
|
|
|
* Data-link level type codes.
|
|
|
|
*/
|
2004-05-30 17:03:48 +00:00
|
|
|
#define DLT_NULL 0 /* BSD loopback encapsulation */
|
1994-05-24 10:09:53 +00:00
|
|
|
#define DLT_EN10MB 1 /* Ethernet (10Mb) */
|
|
|
|
#define DLT_EN3MB 2 /* Experimental Ethernet (3Mb) */
|
|
|
|
#define DLT_AX25 3 /* Amateur Radio AX.25 */
|
|
|
|
#define DLT_PRONET 4 /* Proteon ProNET Token Ring */
|
|
|
|
#define DLT_CHAOS 5 /* Chaos */
|
|
|
|
#define DLT_IEEE802 6 /* IEEE 802 Networks */
|
|
|
|
#define DLT_ARCNET 7 /* ARCNET */
|
|
|
|
#define DLT_SLIP 8 /* Serial Line IP */
|
|
|
|
#define DLT_PPP 9 /* Point-to-point Protocol */
|
|
|
|
#define DLT_FDDI 10 /* FDDI */
|
1996-08-19 20:28:25 +00:00
|
|
|
#define DLT_ATM_RFC1483 11 /* LLC/SNAP encapsulated atm */
|
1998-08-18 10:13:11 +00:00
|
|
|
#define DLT_RAW 12 /* raw IP */
|
2001-07-31 23:27:06 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* These are values from BSD/OS's "bpf.h".
|
|
|
|
* These are not the same as the values from the traditional libpcap
|
|
|
|
* "bpf.h"; however, these values shouldn't be generated by any
|
|
|
|
* OS other than BSD/OS, so the correct values to use here are the
|
|
|
|
* BSD/OS values.
|
|
|
|
*
|
|
|
|
* Platforms that have already assigned these values to other
|
|
|
|
* DLT_ codes, however, should give these codes the values
|
|
|
|
* from that platform, so that programs that use these codes will
|
|
|
|
* continue to compile - even though they won't correctly read
|
|
|
|
* files of these types.
|
|
|
|
*/
|
|
|
|
#define DLT_SLIP_BSDOS 15 /* BSD/OS Serial Line IP */
|
|
|
|
#define DLT_PPP_BSDOS 16 /* BSD/OS Point-to-point Protocol */
|
|
|
|
|
|
|
|
#define DLT_ATM_CLIP 19 /* Linux Classical-IP over ATM */
|
|
|
|
|
|
|
|
/*
|
2002-06-21 05:29:40 +00:00
|
|
|
* These values are defined by NetBSD; other platforms should refrain from
|
|
|
|
* using them for other purposes, so that NetBSD savefiles with link
|
|
|
|
* types of 50 or 51 can be read as this type on all platforms.
|
2001-07-31 23:27:06 +00:00
|
|
|
*/
|
|
|
|
#define DLT_PPP_SERIAL 50 /* PPP over serial with HDLC encapsulation */
|
2002-06-21 05:29:40 +00:00
|
|
|
#define DLT_PPP_ETHER 51 /* PPP over Ethernet */
|
2001-07-31 23:27:06 +00:00
|
|
|
|
2004-03-31 14:22:13 +00:00
|
|
|
/*
|
|
|
|
* Reserved for the Symantec Enterprise Firewall.
|
|
|
|
*/
|
|
|
|
#define DLT_SYMANTEC_FIREWALL 99
|
|
|
|
|
2012-05-14 05:10:41 +00:00
|
|
|
/*
|
|
|
|
* Values between 100 and 103 are used in capture file headers as
|
|
|
|
* link-layer header type LINKTYPE_ values corresponding to DLT_ types
|
|
|
|
* that differ between platforms; don't use those values for new DLT_
|
|
|
|
* new types.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Values starting with 104 are used for newly-assigned link-layer
|
|
|
|
* header type values; for those link-layer header types, the DLT_
|
|
|
|
* value returned by pcap_datalink() and passed to pcap_open_dead(),
|
|
|
|
* and the LINKTYPE_ value that appears in capture files, are the
|
|
|
|
* same.
|
|
|
|
*
|
|
|
|
* DLT_MATCHING_MIN is the lowest such value; DLT_MATCHING_MAX is
|
|
|
|
* the highest such value.
|
|
|
|
*/
|
|
|
|
#define DLT_MATCHING_MIN 104
|
2004-03-31 14:22:13 +00:00
|
|
|
|
2001-07-31 23:27:06 +00:00
|
|
|
/*
|
|
|
|
* This value was defined by libpcap 0.5; platforms that have defined
|
|
|
|
* it with a different value should define it here with that value -
|
|
|
|
* a link type of 104 in a save file will be mapped to DLT_C_HDLC,
|
|
|
|
* whatever value that happens to be, so programs will correctly
|
|
|
|
* handle files with that link type regardless of the value of
|
|
|
|
* DLT_C_HDLC.
|
|
|
|
*
|
|
|
|
* The name DLT_C_HDLC was used by BSD/OS; we use that name for source
|
|
|
|
* compatibility with programs written for BSD/OS.
|
|
|
|
*
|
|
|
|
* libpcap 0.5 defined it as DLT_CHDLC; we define DLT_CHDLC as well,
|
|
|
|
* for source compatibility with programs written for libpcap 0.5.
|
|
|
|
*/
|
|
|
|
#define DLT_C_HDLC 104 /* Cisco HDLC */
|
|
|
|
#define DLT_CHDLC DLT_C_HDLC
|
|
|
|
|
|
|
|
#define DLT_IEEE802_11 105 /* IEEE 802.11 wireless */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Values between 106 and 107 are used in capture file headers as
|
|
|
|
* link-layer types corresponding to DLT_ types that might differ
|
|
|
|
* between platforms; don't use those values for new DLT_ new types.
|
|
|
|
*/
|
|
|
|
|
2004-03-31 14:09:26 +00:00
|
|
|
/*
|
|
|
|
* Frame Relay; BSD/OS has a DLT_FR with a value of 11, but that collides
|
|
|
|
* with other values.
|
|
|
|
* DLT_FR and DLT_FRELAY packets start with the Q.922 Frame Relay header
|
|
|
|
* (DLCI, etc.).
|
|
|
|
*/
|
|
|
|
#define DLT_FRELAY 107
|
|
|
|
|
2001-07-31 23:27:06 +00:00
|
|
|
/*
|
|
|
|
* OpenBSD DLT_LOOP, for loopback devices; it's like DLT_NULL, except
|
|
|
|
* that the AF_ type in the link-layer header is in network byte order.
|
|
|
|
*
|
|
|
|
* OpenBSD defines it as 12, but that collides with DLT_RAW, so we
|
|
|
|
* define it as 108 here. If OpenBSD picks up this file, it should
|
|
|
|
* define DLT_LOOP as 12 in its version, as per the comment above -
|
2002-06-21 05:29:40 +00:00
|
|
|
* and should not use 108 as a DLT_ value.
|
2001-07-31 23:27:06 +00:00
|
|
|
*/
|
|
|
|
#define DLT_LOOP 108
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Values between 109 and 112 are used in capture file headers as
|
|
|
|
* link-layer types corresponding to DLT_ types that might differ
|
|
|
|
* between platforms; don't use those values for new DLT_ new types.
|
|
|
|
*/
|
|
|
|
|
2004-03-31 14:09:26 +00:00
|
|
|
/*
|
|
|
|
* Encapsulated packets for IPsec; DLT_ENC is 13 in OpenBSD, but that's
|
|
|
|
* DLT_SLIP_BSDOS in NetBSD, so we don't use 13 for it in OSes other
|
|
|
|
* than OpenBSD.
|
|
|
|
*/
|
|
|
|
#define DLT_ENC 109
|
|
|
|
|
2001-07-31 23:27:06 +00:00
|
|
|
/*
|
|
|
|
* This is for Linux cooked sockets.
|
|
|
|
*/
|
|
|
|
#define DLT_LINUX_SLL 113
|
1994-05-24 10:09:53 +00:00
|
|
|
|
2002-06-21 05:29:40 +00:00
|
|
|
/*
|
|
|
|
* Apple LocalTalk hardware.
|
|
|
|
*/
|
|
|
|
#define DLT_LTALK 114
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Acorn Econet.
|
|
|
|
*/
|
|
|
|
#define DLT_ECONET 115
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Reserved for use with OpenBSD ipfilter.
|
|
|
|
*/
|
|
|
|
#define DLT_IPFILTER 116
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Reserved for use in capture-file headers as a link-layer type
|
|
|
|
* corresponding to OpenBSD DLT_PFLOG; DLT_PFLOG is 17 in OpenBSD,
|
|
|
|
* but that's DLT_LANE8023 in SuSE 6.3, so we can't use 17 for it
|
|
|
|
* in capture-file headers.
|
|
|
|
*/
|
|
|
|
#define DLT_PFLOG 117
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Registered for Cisco-internal use.
|
|
|
|
*/
|
|
|
|
#define DLT_CISCO_IOS 118
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Reserved 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
|
|
|
|
|
2004-03-31 14:09:26 +00:00
|
|
|
/*
|
|
|
|
* Reserved for use by OpenBSD's pfsync device.
|
|
|
|
*/
|
|
|
|
#define DLT_PFSYNC 121
|
|
|
|
|
2004-03-31 14:22:13 +00:00
|
|
|
/*
|
|
|
|
* Reserved for Siemens HiPath HDLC. XXX
|
|
|
|
*/
|
|
|
|
#define DLT_HHDLC 121
|
|
|
|
|
2004-03-31 14:09:26 +00:00
|
|
|
/*
|
|
|
|
* Reserved for RFC 2625 IP-over-Fibre Channel.
|
|
|
|
*/
|
|
|
|
#define DLT_IP_OVER_FC 122
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Reserved for Full Frontal ATM on Solaris.
|
|
|
|
*/
|
|
|
|
#define DLT_SUNATM 123
|
|
|
|
|
2004-03-31 14:22:13 +00:00
|
|
|
/*
|
|
|
|
* 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 */
|
|
|
|
|
2004-03-31 14:09:26 +00:00
|
|
|
/*
|
|
|
|
* BSD header for 802.11 plus a number of bits of link-layer information
|
|
|
|
* including radio information.
|
|
|
|
*/
|
|
|
|
#ifndef DLT_IEEE802_11_RADIO
|
|
|
|
#define DLT_IEEE802_11_RADIO 127
|
|
|
|
#endif
|
|
|
|
|
2004-03-31 14:22:13 +00:00
|
|
|
/*
|
|
|
|
* Reserved for TZSP encapsulation.
|
|
|
|
*/
|
|
|
|
#define DLT_TZSP 128 /* Tazmen Sniffer Protocol */
|
|
|
|
|
2004-03-31 14:09:26 +00:00
|
|
|
/*
|
|
|
|
* Reserved for Linux ARCNET.
|
|
|
|
*/
|
|
|
|
#define DLT_ARCNET_LINUX 129
|
|
|
|
|
2004-03-31 14:22:13 +00:00
|
|
|
/*
|
|
|
|
* Juniper-private data link types.
|
|
|
|
*/
|
|
|
|
#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
|
|
|
|
|
2004-03-31 14:09:26 +00:00
|
|
|
/*
|
2005-05-28 21:56:41 +00:00
|
|
|
* 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.
|
2004-03-31 14:09:26 +00:00
|
|
|
*/
|
|
|
|
#define DLT_APPLE_IP_OVER_IEEE1394 138
|
|
|
|
|
2005-05-28 21:56:41 +00:00
|
|
|
/*
|
2005-07-11 03:16:23 +00:00
|
|
|
* Various SS7 encapsulations, as per a request from Jeff Morriss
|
|
|
|
* <jeff.morriss[AT]ulticom.com> and subsequent discussions.
|
2005-05-28 21:56:41 +00:00
|
|
|
*/
|
2005-07-11 03:16:23 +00:00
|
|
|
#define DLT_MTP2_WITH_PHDR 139 /* pseudo-header with various info, followed by MTP2 */
|
|
|
|
#define DLT_MTP2 140 /* MTP2, without pseudo-header */
|
|
|
|
#define DLT_MTP3 141 /* MTP3, without pseudo-header or MTP2 */
|
|
|
|
#define DLT_SCCP 142 /* SCCP, without pseudo-header or MTP2 or MTP3 */
|
2005-05-28 21:56:41 +00:00
|
|
|
|
2004-03-31 14:22:13 +00:00
|
|
|
/*
|
|
|
|
* Reserved for DOCSIS.
|
|
|
|
*/
|
|
|
|
#define DLT_DOCSIS 143
|
|
|
|
|
2004-03-31 14:09:26 +00:00
|
|
|
/*
|
|
|
|
* Reserved for Linux IrDA.
|
|
|
|
*/
|
|
|
|
#define DLT_LINUX_IRDA 144
|
|
|
|
|
2004-03-31 14:22:13 +00:00
|
|
|
/*
|
|
|
|
* Reserved for IBM SP switch and IBM Next Federation switch.
|
|
|
|
*/
|
|
|
|
#define DLT_IBM_SP 145
|
|
|
|
#define DLT_IBM_SN 146
|
|
|
|
|
2004-03-31 14:09:26 +00:00
|
|
|
/*
|
2005-05-28 21:56:41 +00:00
|
|
|
* 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 it might be used by some non-AVS drivers now or 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
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Reserved for BACnet MS/TP.
|
|
|
|
*/
|
|
|
|
#define DLT_BACNET_MS_TP 165
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Another PPP variant as per request from Karsten Keil <kkeil@suse.de>.
|
|
|
|
*
|
|
|
|
* This is used in some OSes to allow a kernel socket filter to distinguish
|
|
|
|
* between incoming and outgoing packets, on a socket intended to
|
|
|
|
* supply pppd with outgoing packets so it can do dial-on-demand and
|
|
|
|
* hangup-on-lack-of-demand; incoming packets are filtered out so they
|
|
|
|
* don't cause pppd to hold the connection up (you don't want random
|
|
|
|
* input packets such as port scans, packets from old lost connections,
|
|
|
|
* etc. to force the connection to stay up).
|
|
|
|
*
|
|
|
|
* The first byte of the PPP header (0xff03) is modified to accomodate
|
|
|
|
* the direction - 0x00 = IN, 0x01 = OUT.
|
|
|
|
*/
|
|
|
|
#define DLT_PPP_PPPD 166
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Names for backwards compatibility with older versions of some PPP
|
|
|
|
* software; new software should use DLT_PPP_PPPD.
|
|
|
|
*/
|
|
|
|
#define DLT_PPP_WITH_DIRECTION DLT_PPP_PPPD
|
|
|
|
#define DLT_LINUX_PPP_WITHDIRECTION DLT_PPP_PPPD
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 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, cookies, etc..
|
|
|
|
*/
|
|
|
|
#define DLT_JUNIPER_PPPOE 167
|
|
|
|
#define DLT_JUNIPER_PPPOE_ATM 168
|
|
|
|
|
|
|
|
#define DLT_GPRS_LLC 169 /* GPRS LLC */
|
|
|
|
#define DLT_GPF_T 170 /* GPF-T (ITU-T G.7041/Y.1303) */
|
|
|
|
#define DLT_GPF_F 171 /* GPF-F (ITU-T G.7041/Y.1303) */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Requested by Oolan Zimmer <oz@gcom.com> for use in Gcom's T1/E1 line
|
|
|
|
* monitoring equipment.
|
|
|
|
*/
|
|
|
|
#define DLT_GCOM_T1E1 172
|
|
|
|
#define DLT_GCOM_SERIAL 173
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Juniper-private data link type, as per request from
|
|
|
|
* Hannes Gredler <hannes@juniper.net>. The DLT_ is used
|
|
|
|
* for internal communication to Physical Interface Cards (PIC)
|
2004-03-31 14:09:26 +00:00
|
|
|
*/
|
2005-05-28 21:56:41 +00:00
|
|
|
#define DLT_JUNIPER_PIC_PEER 174
|
2004-03-31 14:09:26 +00:00
|
|
|
|
2004-03-31 14:22:13 +00:00
|
|
|
/*
|
2005-05-28 21:56:41 +00:00
|
|
|
* Link types requested by Gregor Maier <gregor@endace.com> of Endace
|
|
|
|
* Measurement Systems. They add an ERF header (see
|
|
|
|
* http://www.endace.com/support/EndaceRecordFormat.pdf) in front of
|
|
|
|
* the link-layer header.
|
2004-03-31 14:22:13 +00:00
|
|
|
*/
|
2005-05-28 21:56:41 +00:00
|
|
|
#define DLT_ERF_ETH 175 /* Ethernet */
|
|
|
|
#define DLT_ERF_POS 176 /* Packet-over-SONET */
|
2004-03-31 14:22:13 +00:00
|
|
|
|
2005-07-11 03:16:23 +00:00
|
|
|
/*
|
|
|
|
* Requested by Daniele Orlandi <daniele@orlandi.com> for raw LAPD
|
|
|
|
* for vISDN (http://www.orlandi.com/visdn/). Its link-layer header
|
|
|
|
* includes additional information before the LAPD header, so it's
|
|
|
|
* not necessarily a generic LAPD header.
|
|
|
|
*/
|
|
|
|
#define DLT_LINUX_LAPD 177
|
|
|
|
|
2006-09-04 19:24:34 +00:00
|
|
|
/*
|
|
|
|
* Juniper-private data link type, as per request from
|
2007-12-23 14:10:33 +00:00
|
|
|
* Hannes Gredler <hannes@juniper.net>.
|
2006-09-04 19:24:34 +00:00
|
|
|
* The DLT_ are used for prepending meta-information
|
|
|
|
* like interface index, interface name
|
|
|
|
* before standard Ethernet, PPP, Frelay & C-HDLC Frames
|
|
|
|
*/
|
|
|
|
#define DLT_JUNIPER_ETHER 178
|
|
|
|
#define DLT_JUNIPER_PPP 179
|
|
|
|
#define DLT_JUNIPER_FRELAY 180
|
|
|
|
#define DLT_JUNIPER_CHDLC 181
|
|
|
|
|
2007-10-21 13:23:32 +00:00
|
|
|
/*
|
|
|
|
* Multi Link Frame Relay (FRF.16)
|
|
|
|
*/
|
|
|
|
#define DLT_MFR 182
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Juniper-private data link type, as per request from
|
2007-12-23 14:10:33 +00:00
|
|
|
* Hannes Gredler <hannes@juniper.net>.
|
2007-10-21 13:23:32 +00:00
|
|
|
* The DLT_ is used for internal communication with a
|
|
|
|
* voice Adapter Card (PIC)
|
|
|
|
*/
|
|
|
|
#define DLT_JUNIPER_VP 183
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Arinc 429 frames.
|
|
|
|
* DLT_ requested by Gianluca Varenni <gianluca.varenni@cacetech.com>.
|
|
|
|
* Every frame contains a 32bit A429 label.
|
|
|
|
* More documentation on Arinc 429 can be found at
|
|
|
|
* http://www.condoreng.com/support/downloads/tutorials/ARINCTutorial.pdf
|
|
|
|
*/
|
|
|
|
#define DLT_A429 184
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Arinc 653 Interpartition Communication messages.
|
|
|
|
* DLT_ requested by Gianluca Varenni <gianluca.varenni@cacetech.com>.
|
|
|
|
* Please refer to the A653-1 standard for more information.
|
|
|
|
*/
|
|
|
|
#define DLT_A653_ICM 185
|
|
|
|
|
|
|
|
/*
|
|
|
|
* USB packets, beginning with a USB setup header; requested by
|
|
|
|
* Paolo Abeni <paolo.abeni@email.it>.
|
|
|
|
*/
|
|
|
|
#define DLT_USB 186
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Bluetooth HCI UART transport layer (part H:4); requested by
|
|
|
|
* Paolo Abeni.
|
|
|
|
*/
|
|
|
|
#define DLT_BLUETOOTH_HCI_H4 187
|
|
|
|
|
|
|
|
/*
|
|
|
|
* IEEE 802.16 MAC Common Part Sublayer; requested by Maria Cruz
|
|
|
|
* <cruz_petagay@bah.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_IEEE802_16_MAC_CPS 188
|
|
|
|
|
|
|
|
/*
|
|
|
|
* USB packets, beginning with a Linux USB header; requested by
|
|
|
|
* Paolo Abeni <paolo.abeni@email.it>.
|
|
|
|
*/
|
|
|
|
#define DLT_USB_LINUX 189
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Controller Area Network (CAN) v. 2.0B packets.
|
|
|
|
* DLT_ requested by Gianluca Varenni <gianluca.varenni@cacetech.com>.
|
|
|
|
* Used to dump CAN packets coming from a CAN Vector board.
|
|
|
|
* More documentation on the CAN v2.0B frames can be found at
|
|
|
|
* http://www.can-cia.org/downloads/?269
|
|
|
|
*/
|
|
|
|
#define DLT_CAN20B 190
|
|
|
|
|
|
|
|
/*
|
|
|
|
* IEEE 802.15.4, with address fields padded, as is done by Linux
|
|
|
|
* drivers; requested by Juergen Schimmer.
|
|
|
|
*/
|
|
|
|
#define DLT_IEEE802_15_4_LINUX 191
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Per Packet Information encapsulated packets.
|
|
|
|
* DLT_ requested by Gianluca Varenni <gianluca.varenni@cacetech.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_PPI 192
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Header for 802.16 MAC Common Part Sublayer plus a radiotap radio header;
|
|
|
|
* requested by Charles Clancy.
|
|
|
|
*/
|
|
|
|
#define DLT_IEEE802_16_MAC_CPS_RADIO 193
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Juniper-private data link type, as per request from
|
2007-12-23 14:10:33 +00:00
|
|
|
* Hannes Gredler <hannes@juniper.net>.
|
2007-10-21 13:23:32 +00:00
|
|
|
* The DLT_ is used for internal communication with a
|
|
|
|
* integrated service module (ISM).
|
|
|
|
*/
|
|
|
|
#define DLT_JUNIPER_ISM 194
|
|
|
|
|
|
|
|
/*
|
|
|
|
* IEEE 802.15.4, exactly as it appears in the spec (no padding, no
|
|
|
|
* nothing); requested by Mikko Saarnivala <mikko.saarnivala@sensinode.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_IEEE802_15_4 195
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Various link-layer types, with a pseudo-header, for SITA
|
|
|
|
* (http://www.sita.aero/); requested by Fulko Hew (fulko.hew@gmail.com).
|
|
|
|
*/
|
|
|
|
#define DLT_SITA 196
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Various link-layer types, with a pseudo-header, for Endace DAG cards;
|
|
|
|
* encapsulates Endace ERF records. Requested by Stephen Donnelly
|
|
|
|
* <stephen@endace.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_ERF 197
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Special header prepended to Ethernet packets when capturing from a
|
|
|
|
* u10 Networks board. Requested by Phil Mulholland
|
|
|
|
* <phil@u10networks.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_RAIF1 198
|
|
|
|
|
|
|
|
/*
|
|
|
|
* IPMB packet for IPMI, beginning with the I2C slave address, followed
|
|
|
|
* by the netFn and LUN, etc.. Requested by Chanthy Toeung
|
|
|
|
* <chanthy.toeung@ca.kontron.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_IPMB 199
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Juniper-private data link type, as per request from
|
2007-12-23 14:10:33 +00:00
|
|
|
* Hannes Gredler <hannes@juniper.net>.
|
2007-10-21 13:23:32 +00:00
|
|
|
* The DLT_ is used for capturing data on a secure tunnel interface.
|
|
|
|
*/
|
|
|
|
#define DLT_JUNIPER_ST 200
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Bluetooth HCI UART transport layer (part H:4), with pseudo-header
|
|
|
|
* that includes direction information; requested by Paolo Abeni.
|
|
|
|
*/
|
|
|
|
#define DLT_BLUETOOTH_HCI_H4_WITH_PHDR 201
|
|
|
|
|
2009-04-02 13:02:12 +00:00
|
|
|
/*
|
|
|
|
* AX.25 packet with a 1-byte KISS header; see
|
|
|
|
*
|
|
|
|
* http://www.ax25.net/kiss.htm
|
|
|
|
*
|
|
|
|
* as per Richard Stearn <richard@rns-stearn.demon.co.uk>.
|
|
|
|
*/
|
|
|
|
#define DLT_AX25_KISS 202
|
|
|
|
|
|
|
|
/*
|
|
|
|
* LAPD packets from an ISDN channel, starting with the address field,
|
|
|
|
* with no pseudo-header.
|
|
|
|
* Requested by Varuna De Silva <varunax@gmail.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_LAPD 203
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Variants of various link-layer headers, with a one-byte direction
|
|
|
|
* pseudo-header prepended - zero means "received by this host",
|
|
|
|
* non-zero (any non-zero value) means "sent by this host" - as per
|
|
|
|
* Will Barker <w.barker@zen.co.uk>.
|
|
|
|
*/
|
|
|
|
#define DLT_PPP_WITH_DIR 204 /* PPP - don't confuse with DLT_PPP_WITH_DIRECTION */
|
|
|
|
#define DLT_C_HDLC_WITH_DIR 205 /* Cisco HDLC */
|
|
|
|
#define DLT_FRELAY_WITH_DIR 206 /* Frame Relay */
|
|
|
|
#define DLT_LAPB_WITH_DIR 207 /* LAPB */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 208 is reserved for an as-yet-unspecified proprietary link-layer
|
|
|
|
* type, as requested by Will Barker.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* IPMB with a Linux-specific pseudo-header; as requested by Alexey Neyman
|
|
|
|
* <avn@pigeonpoint.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_IPMB_LINUX 209
|
|
|
|
|
|
|
|
/*
|
|
|
|
* FlexRay automotive bus - http://www.flexray.com/ - as requested
|
|
|
|
* by Hannes Kaelber <hannes.kaelber@x2e.de>.
|
|
|
|
*/
|
|
|
|
#define DLT_FLEXRAY 210
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Media Oriented Systems Transport (MOST) bus for multimedia
|
|
|
|
* transport - http://www.mostcooperation.com/ - as requested
|
|
|
|
* by Hannes Kaelber <hannes.kaelber@x2e.de>.
|
|
|
|
*/
|
|
|
|
#define DLT_MOST 211
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Local Interconnect Network (LIN) bus for vehicle networks -
|
|
|
|
* http://www.lin-subbus.org/ - as requested by Hannes Kaelber
|
|
|
|
* <hannes.kaelber@x2e.de>.
|
|
|
|
*/
|
|
|
|
#define DLT_LIN 212
|
|
|
|
|
|
|
|
/*
|
|
|
|
* X2E-private data link type used for serial line capture,
|
|
|
|
* as requested by Hannes Kaelber <hannes.kaelber@x2e.de>.
|
|
|
|
*/
|
|
|
|
#define DLT_X2E_SERIAL 213
|
|
|
|
|
|
|
|
/*
|
|
|
|
* X2E-private data link type used for the Xoraya data logger
|
|
|
|
* family, as requested by Hannes Kaelber <hannes.kaelber@x2e.de>.
|
|
|
|
*/
|
|
|
|
#define DLT_X2E_XORAYA 214
|
|
|
|
|
|
|
|
/*
|
|
|
|
* IEEE 802.15.4, exactly as it appears in the spec (no padding, no
|
|
|
|
* nothing), but with the PHY-level data for non-ASK PHYs (4 octets
|
|
|
|
* of 0 as preamble, one octet of SFD, one octet of frame length+
|
|
|
|
* reserved bit, and then the MAC-layer data, starting with the
|
|
|
|
* frame control field).
|
|
|
|
*
|
|
|
|
* Requested by Max Filippov <jcmvbkbc@gmail.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_IEEE802_15_4_NONASK_PHY 215
|
|
|
|
|
2010-10-29 18:41:09 +00:00
|
|
|
/*
|
|
|
|
* David Gibson <david@gibson.dropbear.id.au> requested this for
|
|
|
|
* captures from the Linux kernel /dev/input/eventN devices. This
|
|
|
|
* is used to communicate keystrokes and mouse movements from the
|
|
|
|
* Linux kernel to display systems, such as Xorg.
|
|
|
|
*/
|
|
|
|
#define DLT_LINUX_EVDEV 216
|
|
|
|
|
|
|
|
/*
|
|
|
|
* GSM Um and Abis interfaces, preceded by a "gsmtap" header.
|
|
|
|
*
|
|
|
|
* Requested by Harald Welte <laforge@gnumonks.org>.
|
|
|
|
*/
|
|
|
|
#define DLT_GSMTAP_UM 217
|
|
|
|
#define DLT_GSMTAP_ABIS 218
|
|
|
|
|
|
|
|
/*
|
|
|
|
* MPLS, with an MPLS label as the link-layer header.
|
|
|
|
* Requested by Michele Marchetto <michele@openbsd.org> on behalf
|
|
|
|
* of OpenBSD.
|
|
|
|
*/
|
|
|
|
#define DLT_MPLS 219
|
|
|
|
|
|
|
|
/*
|
|
|
|
* USB packets, beginning with a Linux USB header, with the USB header
|
|
|
|
* padded to 64 bytes; required for memory-mapped access.
|
|
|
|
*/
|
|
|
|
#define DLT_USB_LINUX_MMAPPED 220
|
|
|
|
|
|
|
|
/*
|
|
|
|
* DECT packets, with a pseudo-header; requested by
|
|
|
|
* Matthias Wenzel <tcpdump@mazzoo.de>.
|
|
|
|
*/
|
|
|
|
#define DLT_DECT 221
|
|
|
|
/*
|
|
|
|
* From: "Lidwa, Eric (GSFC-582.0)[SGT INC]" <eric.lidwa-1@nasa.gov>
|
|
|
|
* Date: Mon, 11 May 2009 11:18:30 -0500
|
|
|
|
*
|
|
|
|
* DLT_AOS. We need it for AOS Space Data Link Protocol.
|
|
|
|
* I have already written dissectors for but need an OK from
|
|
|
|
* legal before I can submit a patch.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
#define DLT_AOS 222
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Wireless HART (Highway Addressable Remote Transducer)
|
|
|
|
* From the HART Communication Foundation
|
|
|
|
* IES/PAS 62591
|
|
|
|
*
|
|
|
|
* Requested by Sam Roberts <vieuxtech@gmail.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_WIHART 223
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Fibre Channel FC-2 frames, beginning with a Frame_Header.
|
|
|
|
* Requested by Kahou Lei <kahou82@gmail.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_FC_2 224
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Fibre Channel FC-2 frames, beginning with an encoding of the
|
|
|
|
* SOF, and ending with an encoding of the EOF.
|
|
|
|
*
|
|
|
|
* The encodings represent the frame delimiters as 4-byte sequences
|
|
|
|
* representing the corresponding ordered sets, with K28.5
|
|
|
|
* represented as 0xBC, and the D symbols as the corresponding
|
|
|
|
* byte values; for example, SOFi2, which is K28.5 - D21.5 - D1.2 - D21.2,
|
|
|
|
* is represented as 0xBC 0xB5 0x55 0x55.
|
|
|
|
*
|
|
|
|
* Requested by Kahou Lei <kahou82@gmail.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_FC_2_WITH_FRAME_DELIMS 225
|
|
|
|
/*
|
|
|
|
* Solaris ipnet pseudo-header; requested by Darren Reed <Darren.Reed@Sun.COM>.
|
|
|
|
*
|
|
|
|
* The pseudo-header starts with a one-byte version number; for version 2,
|
|
|
|
* the pseudo-header is:
|
|
|
|
*
|
|
|
|
* struct dl_ipnetinfo {
|
|
|
|
* u_int8_t dli_version;
|
|
|
|
* u_int8_t dli_family;
|
|
|
|
* u_int16_t dli_htype;
|
|
|
|
* u_int32_t dli_pktlen;
|
|
|
|
* u_int32_t dli_ifindex;
|
|
|
|
* u_int32_t dli_grifindex;
|
|
|
|
* u_int32_t dli_zsrc;
|
|
|
|
* u_int32_t dli_zdst;
|
|
|
|
* };
|
|
|
|
*
|
|
|
|
* dli_version is 2 for the current version of the pseudo-header.
|
|
|
|
*
|
|
|
|
* dli_family is a Solaris address family value, so it's 2 for IPv4
|
|
|
|
* and 26 for IPv6.
|
|
|
|
*
|
|
|
|
* dli_htype is a "hook type" - 0 for incoming packets, 1 for outgoing
|
|
|
|
* packets, and 2 for packets arriving from another zone on the same
|
|
|
|
* machine.
|
|
|
|
*
|
|
|
|
* dli_pktlen is the length of the packet data following the pseudo-header
|
|
|
|
* (so the captured length minus dli_pktlen is the length of the
|
|
|
|
* pseudo-header, assuming the entire pseudo-header was captured).
|
|
|
|
*
|
|
|
|
* dli_ifindex is the interface index of the interface on which the
|
|
|
|
* packet arrived.
|
|
|
|
*
|
|
|
|
* dli_grifindex is the group interface index number (for IPMP interfaces).
|
|
|
|
*
|
|
|
|
* dli_zsrc is the zone identifier for the source of the packet.
|
|
|
|
*
|
|
|
|
* dli_zdst is the zone identifier for the destination of the packet.
|
|
|
|
*
|
|
|
|
* A zone number of 0 is the global zone; a zone number of 0xffffffff
|
|
|
|
* means that the packet arrived from another host on the network, not
|
|
|
|
* from another zone on the same machine.
|
|
|
|
*
|
|
|
|
* An IPv4 or IPv6 datagram follows the pseudo-header; dli_family indicates
|
|
|
|
* which of those it is.
|
|
|
|
*/
|
|
|
|
#define DLT_IPNET 226
|
|
|
|
|
|
|
|
/*
|
|
|
|
* CAN (Controller Area Network) frames, with a pseudo-header as supplied
|
|
|
|
* by Linux SocketCAN. See Documentation/networking/can.txt in the Linux
|
|
|
|
* source.
|
|
|
|
*
|
|
|
|
* Requested by Felix Obenhuber <felix@obenhuber.de>.
|
|
|
|
*/
|
|
|
|
#define DLT_CAN_SOCKETCAN 227
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Raw IPv4/IPv6; different from DLT_RAW in that the DLT_ value specifies
|
|
|
|
* whether it's v4 or v6. Requested by Darren Reed <Darren.Reed@Sun.COM>.
|
|
|
|
*/
|
2012-05-14 05:10:41 +00:00
|
|
|
#define DLT_IPV4 228
|
|
|
|
#define DLT_IPV6 229
|
|
|
|
|
|
|
|
/*
|
|
|
|
* IEEE 802.15.4, exactly as it appears in the spec (no padding, no
|
|
|
|
* nothing), and with no FCS at the end of the frame; requested by
|
|
|
|
* Jon Smirl <jonsmirl@gmail.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_IEEE802_15_4_NOFCS 230
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Raw D-Bus:
|
|
|
|
*
|
|
|
|
* http://www.freedesktop.org/wiki/Software/dbus
|
|
|
|
*
|
|
|
|
* messages:
|
|
|
|
*
|
|
|
|
* http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-messages
|
|
|
|
*
|
|
|
|
* starting with the endianness flag, followed by the message type, etc.,
|
|
|
|
* but without the authentication handshake before the message sequence:
|
|
|
|
*
|
|
|
|
* http://dbus.freedesktop.org/doc/dbus-specification.html#auth-protocol
|
|
|
|
*
|
|
|
|
* Requested by Martin Vidner <martin@vidner.net>.
|
|
|
|
*/
|
|
|
|
#define DLT_DBUS 231
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Juniper-private data link type, as per request from
|
|
|
|
* Hannes Gredler <hannes@juniper.net>.
|
|
|
|
*/
|
|
|
|
#define DLT_JUNIPER_VS 232
|
|
|
|
#define DLT_JUNIPER_SRX_E2E 233
|
|
|
|
#define DLT_JUNIPER_FIBRECHANNEL 234
|
|
|
|
|
|
|
|
/*
|
|
|
|
* DVB-CI (DVB Common Interface for communication between a PC Card
|
|
|
|
* module and a DVB receiver). See
|
|
|
|
*
|
|
|
|
* http://www.kaiser.cx/pcap-dvbci.html
|
|
|
|
*
|
|
|
|
* for the specification.
|
|
|
|
*
|
|
|
|
* Requested by Martin Kaiser <martin@kaiser.cx>.
|
|
|
|
*/
|
|
|
|
#define DLT_DVB_CI 235
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Variant of 3GPP TS 27.010 multiplexing protocol (similar to, but
|
|
|
|
* *not* the same as, 27.010). Requested by Hans-Christoph Schemmel
|
|
|
|
* <hans-christoph.schemmel@cinterion.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_MUX27010 236
|
|
|
|
|
|
|
|
/*
|
|
|
|
* STANAG 5066 D_PDUs. Requested by M. Baris Demiray
|
|
|
|
* <barisdemiray@gmail.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_STANAG_5066_D_PDU 237
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Juniper-private data link type, as per request from
|
|
|
|
* Hannes Gredler <hannes@juniper.net>.
|
|
|
|
*/
|
|
|
|
#define DLT_JUNIPER_ATM_CEMIC 238
|
|
|
|
|
|
|
|
/*
|
|
|
|
* NetFilter LOG messages
|
|
|
|
* (payload of netlink NFNL_SUBSYS_ULOG/NFULNL_MSG_PACKET packets)
|
|
|
|
*
|
|
|
|
* Requested by Jakub Zawadzki <darkjames-ws@darkjames.pl>
|
|
|
|
*/
|
|
|
|
#define DLT_NFLOG 239
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Hilscher Gesellschaft fuer Systemautomation mbH link-layer type
|
|
|
|
* for Ethernet packets with a 4-byte pseudo-header and always
|
|
|
|
* with the payload including the FCS, as supplied by their
|
|
|
|
* netANALYZER hardware and software.
|
|
|
|
*
|
|
|
|
* Requested by Holger P. Frommer <HPfrommer@hilscher.com>
|
|
|
|
*/
|
|
|
|
#define DLT_NETANALYZER 240
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Hilscher Gesellschaft fuer Systemautomation mbH link-layer type
|
|
|
|
* for Ethernet packets with a 4-byte pseudo-header and FCS and
|
|
|
|
* with the Ethernet header preceded by 7 bytes of preamble and
|
|
|
|
* 1 byte of SFD, as supplied by their netANALYZER hardware and
|
|
|
|
* software.
|
|
|
|
*
|
|
|
|
* Requested by Holger P. Frommer <HPfrommer@hilscher.com>
|
|
|
|
*/
|
|
|
|
#define DLT_NETANALYZER_TRANSPARENT 241
|
|
|
|
|
|
|
|
/*
|
2013-05-30 06:41:26 +00:00
|
|
|
* IP-over-InfiniBand, as specified by RFC 4391.
|
2012-05-14 05:10:41 +00:00
|
|
|
*
|
|
|
|
* Requested by Petr Sumbera <petr.sumbera@oracle.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_IPOIB 242
|
|
|
|
|
2012-10-04 21:07:56 +00:00
|
|
|
/*
|
|
|
|
* MPEG-2 transport stream (ISO 13818-1/ITU-T H.222.0).
|
|
|
|
*
|
|
|
|
* Requested by Guy Martin <gmsoft@tuxicoman.be>.
|
|
|
|
*/
|
|
|
|
#define DLT_MPEG_2_TS 243
|
|
|
|
|
|
|
|
/*
|
|
|
|
* ng4T GmbH's UMTS Iub/Iur-over-ATM and Iub/Iur-over-IP format as
|
|
|
|
* used by their ng40 protocol tester.
|
|
|
|
*
|
|
|
|
* Requested by Jens Grimmer <jens.grimmer@ng4t.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_NG40 244
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Pseudo-header giving adapter number and flags, followed by an NFC
|
|
|
|
* (Near-Field Communications) Logical Link Control Protocol (LLCP) PDU,
|
|
|
|
* as specified by NFC Forum Logical Link Control Protocol Technical
|
|
|
|
* Specification LLCP 1.1.
|
|
|
|
*
|
|
|
|
* Requested by Mike Wakerly <mikey@google.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_NFC_LLCP 245
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 245 is used as LINKTYPE_PFSYNC; do not use it for any other purpose.
|
|
|
|
*
|
|
|
|
* DLT_PFSYNC has different values on different platforms, and all of
|
|
|
|
* them collide with something used elsewhere. On platforms that
|
|
|
|
* don't already define it, define it as 245.
|
|
|
|
*/
|
|
|
|
#if !defined(__FreeBSD__) && !defined(__OpenBSD__) && !defined(__NetBSD__) && !defined(__DragonFly__) && !defined(__APPLE__)
|
|
|
|
#define DLT_PFSYNC 246
|
|
|
|
#endif
|
|
|
|
|
2013-05-30 06:41:26 +00:00
|
|
|
/*
|
|
|
|
* Raw InfiniBand packets, starting with the Local Routing Header.
|
|
|
|
*
|
|
|
|
* Requested by Oren Kladnitsky <orenk@mellanox.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_INFINIBAND 247
|
|
|
|
|
|
|
|
/*
|
|
|
|
* SCTP, with no lower-level protocols (i.e., no IPv4 or IPv6).
|
|
|
|
*
|
|
|
|
* Requested by Michael Tuexen <Michael.Tuexen@lurchi.franken.de>.
|
|
|
|
*/
|
|
|
|
#define DLT_SCTP 248
|
|
|
|
|
2015-01-06 18:58:31 +00:00
|
|
|
/*
|
|
|
|
* USB packets, beginning with a USBPcap header.
|
|
|
|
*
|
|
|
|
* Requested by Tomasz Mon <desowin@gmail.com>
|
|
|
|
*/
|
|
|
|
#define DLT_USBPCAP 249
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Schweitzer Engineering Laboratories "RTAC" product serial-line
|
|
|
|
* packets.
|
|
|
|
*
|
|
|
|
* Requested by Chris Bontje <chris_bontje@selinc.com>.
|
|
|
|
*/
|
|
|
|
#define DLT_RTAC_SERIAL 250
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Bluetooth Low Energy air interface link-layer packets.
|
|
|
|
*
|
|
|
|
* Requested by Mike Kershaw <dragorn@kismetwireless.net>.
|
|
|
|
*/
|
|
|
|
#define DLT_BLUETOOTH_LE_LL 251
|
|
|
|
|
|
|
|
/*
|
|
|
|
* DLT type for upper-protocol layer PDU saves from wireshark.
|
|
|
|
*
|
|
|
|
* the actual contents are determined by two TAGs stored with each
|
|
|
|
* packet:
|
|
|
|
* EXP_PDU_TAG_LINKTYPE the link type (LINKTYPE_ value) of the
|
|
|
|
* original packet.
|
|
|
|
*
|
|
|
|
* EXP_PDU_TAG_PROTO_NAME the name of the wireshark dissector
|
|
|
|
* that can make sense of the data stored.
|
|
|
|
*/
|
|
|
|
#define DLT_WIRESHARK_UPPER_PDU 252
|
|
|
|
|
|
|
|
/*
|
|
|
|
* DLT type for the netlink protocol (nlmon devices).
|
|
|
|
*/
|
|
|
|
#define DLT_NETLINK 253
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Bluetooth Linux Monitor headers for the BlueZ stack.
|
|
|
|
*/
|
|
|
|
#define DLT_BLUETOOTH_LINUX_MONITOR 254
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Bluetooth Basic Rate/Enhanced Data Rate baseband packets, as
|
|
|
|
* captured by Ubertooth.
|
|
|
|
*/
|
|
|
|
#define DLT_BLUETOOTH_BREDR_BB 255
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Bluetooth Low Energy link layer packets, as captured by Ubertooth.
|
|
|
|
*/
|
|
|
|
#define DLT_BLUETOOTH_LE_LL_WITH_PHDR 256
|
|
|
|
|
|
|
|
/*
|
|
|
|
* PROFIBUS data link layer.
|
|
|
|
*/
|
|
|
|
#define DLT_PROFIBUS_DL 257
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Apple's DLT_PKTAP headers.
|
|
|
|
*
|
|
|
|
* Sadly, the folks at Apple either had no clue that the DLT_USERn values
|
|
|
|
* are for internal use within an organization and partners only, and
|
|
|
|
* didn't know that the right way to get a link-layer header type is to
|
|
|
|
* ask tcpdump.org for one, or knew and didn't care, so they just
|
|
|
|
* used DLT_USER2, which causes problems for everything except for
|
|
|
|
* their version of tcpdump.
|
|
|
|
*
|
|
|
|
* So I'll just give them one; hopefully this will show up in a
|
|
|
|
* libpcap release in time for them to get this into 10.10 Big Sur
|
|
|
|
* or whatever Mavericks' successor is called. LINKTYPE_PKTAP
|
|
|
|
* will be 258 *even on OS X*; that is *intentional*, so that
|
|
|
|
* PKTAP files look the same on *all* OSes (different OSes can have
|
|
|
|
* different numerical values for a given DLT_, but *MUST NOT* have
|
|
|
|
* different values for what goes in a file, as files can be moved
|
|
|
|
* between OSes!).
|
|
|
|
*
|
|
|
|
* When capturing, on a system with a Darwin-based OS, on a device
|
|
|
|
* that returns 149 (DLT_USER2 and Apple's DLT_PKTAP) with this
|
|
|
|
* version of libpcap, the DLT_ value for the pcap_t will be DLT_PKTAP,
|
|
|
|
* and that will continue to be DLT_USER2 on Darwin-based OSes. That way,
|
|
|
|
* binary compatibility with Mavericks is preserved for programs using
|
|
|
|
* this version of libpcap. This does mean that if you were using
|
|
|
|
* DLT_USER2 for some capture device on OS X, you can't do so with
|
|
|
|
* this version of libpcap, just as you can't with Apple's libpcap -
|
|
|
|
* on OS X, they define DLT_PKTAP to be DLT_USER2, so programs won't
|
|
|
|
* be able to distinguish between PKTAP and whatever you were using
|
|
|
|
* DLT_USER2 for.
|
|
|
|
*
|
|
|
|
* If the program saves the capture to a file using this version of
|
|
|
|
* libpcap's pcap_dump code, the LINKTYPE_ value in the file will be
|
|
|
|
* LINKTYPE_PKTAP, which will be 258, even on Darwin-based OSes.
|
|
|
|
* That way, the file will *not* be a DLT_USER2 file. That means
|
|
|
|
* that the latest version of tcpdump, when built with this version
|
|
|
|
* of libpcap, and sufficiently recent versions of Wireshark will
|
|
|
|
* be able to read those files and interpret them correctly; however,
|
|
|
|
* Apple's version of tcpdump in OS X 10.9 won't be able to handle
|
|
|
|
* them. (Hopefully, Apple will pick up this version of libpcap,
|
|
|
|
* and the corresponding version of tcpdump, so that tcpdump will
|
|
|
|
* be able to handle the old LINKTYPE_USER2 captures *and* the new
|
|
|
|
* LINKTYPE_PKTAP captures.)
|
|
|
|
*/
|
|
|
|
#ifdef __APPLE__
|
|
|
|
#define DLT_PKTAP DLT_USER2
|
|
|
|
#else
|
|
|
|
#define DLT_PKTAP 258
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Ethernet packets preceded by a header giving the last 6 octets
|
|
|
|
* of the preamble specified by 802.3-2012 Clause 65, section
|
|
|
|
* 65.1.3.2 "Transmit".
|
|
|
|
*/
|
|
|
|
#define DLT_EPON 259
|
|
|
|
|
|
|
|
/*
|
|
|
|
* IPMI trace packets, as specified by Table 3-20 "Trace Data Block Format"
|
|
|
|
* in the PICMG HPM.2 specification.
|
|
|
|
*/
|
|
|
|
#define DLT_IPMI_HPM_2 260
|
|
|
|
|
|
|
|
#define DLT_MATCHING_MAX 260 /* highest value in the "matching" range */
|
2010-10-29 18:41:09 +00:00
|
|
|
|
2009-04-02 13:02:12 +00:00
|
|
|
/*
|
|
|
|
* DLT and savefile link type values are split into a class and
|
|
|
|
* a member of that class. A class value of 0 indicates a regular
|
|
|
|
* DLT_/LINKTYPE_ value.
|
|
|
|
*/
|
|
|
|
#define DLT_CLASS(x) ((x) & 0x03ff0000)
|
|
|
|
|
1994-05-24 10:09:53 +00:00
|
|
|
/*
|
1996-01-30 23:02:38 +00:00
|
|
|
* The instruction encodings.
|
2015-01-06 18:58:31 +00:00
|
|
|
*
|
|
|
|
* Please inform tcpdump-workers@lists.tcpdump.org if you use any
|
|
|
|
* of the reserved values, so that we can note that they're used
|
|
|
|
* (and perhaps implement it in the reference BPF implementation
|
|
|
|
* and encourage its implementation elsewhere).
|
1994-05-24 10:09:53 +00:00
|
|
|
*/
|
2015-01-06 18:58:31 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* The upper 8 bits of the opcode aren't used. BSD/OS used 0x8000.
|
2009-03-21 20:43:56 +00:00
|
|
|
*/
|
2015-01-06 18:58:31 +00:00
|
|
|
|
1994-05-24 10:09:53 +00:00
|
|
|
/* 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
|
2015-01-06 18:58:31 +00:00
|
|
|
/* 0x18 reserved; used by BSD/OS */
|
1994-05-24 10:09:53 +00:00
|
|
|
#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
|
2015-01-06 18:58:31 +00:00
|
|
|
/* 0xc0 reserved; used by BSD/OS */
|
|
|
|
/* 0xe0 reserved; used by BSD/OS */
|
1994-05-24 10:09:53 +00:00
|
|
|
|
|
|
|
/* 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
|
2015-01-06 18:58:31 +00:00
|
|
|
#define BPF_MOD 0x90
|
|
|
|
#define BPF_XOR 0xa0
|
|
|
|
/* 0xb0 reserved */
|
|
|
|
/* 0xc0 reserved */
|
|
|
|
/* 0xd0 reserved */
|
|
|
|
/* 0xe0 reserved */
|
|
|
|
/* 0xf0 reserved */
|
|
|
|
|
1994-05-24 10:09:53 +00:00
|
|
|
#define BPF_JA 0x00
|
|
|
|
#define BPF_JEQ 0x10
|
|
|
|
#define BPF_JGT 0x20
|
|
|
|
#define BPF_JGE 0x30
|
|
|
|
#define BPF_JSET 0x40
|
2015-01-06 18:58:31 +00:00
|
|
|
/* 0x50 reserved; used on BSD/OS */
|
|
|
|
/* 0x60 reserved */
|
|
|
|
/* 0x70 reserved */
|
|
|
|
/* 0x80 reserved */
|
|
|
|
/* 0x90 reserved */
|
|
|
|
/* 0xa0 reserved */
|
|
|
|
/* 0xb0 reserved */
|
|
|
|
/* 0xc0 reserved */
|
|
|
|
/* 0xd0 reserved */
|
|
|
|
/* 0xe0 reserved */
|
|
|
|
/* 0xf0 reserved */
|
1994-05-24 10:09:53 +00:00
|
|
|
#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
|
2015-01-06 18:58:31 +00:00
|
|
|
/* 0x18 reserved */
|
1994-05-24 10:09:53 +00:00
|
|
|
|
|
|
|
/* misc */
|
|
|
|
#define BPF_MISCOP(code) ((code) & 0xf8)
|
|
|
|
#define BPF_TAX 0x00
|
2015-01-06 18:58:31 +00:00
|
|
|
/* 0x08 reserved */
|
|
|
|
/* 0x10 reserved */
|
|
|
|
/* 0x18 reserved */
|
|
|
|
/* #define BPF_COP 0x20 NetBSD "coprocessor" extensions */
|
|
|
|
/* 0x28 reserved */
|
|
|
|
/* 0x30 reserved */
|
|
|
|
/* 0x38 reserved */
|
|
|
|
/* #define BPF_COPX 0x40 NetBSD "coprocessor" extensions */
|
|
|
|
/* also used on BSD/OS */
|
|
|
|
/* 0x48 reserved */
|
|
|
|
/* 0x50 reserved */
|
|
|
|
/* 0x58 reserved */
|
|
|
|
/* 0x60 reserved */
|
|
|
|
/* 0x68 reserved */
|
|
|
|
/* 0x70 reserved */
|
|
|
|
/* 0x78 reserved */
|
1994-05-24 10:09:53 +00:00
|
|
|
#define BPF_TXA 0x80
|
2015-01-06 18:58:31 +00:00
|
|
|
/* 0x88 reserved */
|
|
|
|
/* 0x90 reserved */
|
|
|
|
/* 0x98 reserved */
|
|
|
|
/* 0xa0 reserved */
|
|
|
|
/* 0xa8 reserved */
|
|
|
|
/* 0xb0 reserved */
|
|
|
|
/* 0xb8 reserved */
|
|
|
|
/* 0xc0 reserved; used on BSD/OS */
|
|
|
|
/* 0xc8 reserved */
|
|
|
|
/* 0xd0 reserved */
|
|
|
|
/* 0xd8 reserved */
|
|
|
|
/* 0xe0 reserved */
|
|
|
|
/* 0xe8 reserved */
|
|
|
|
/* 0xf0 reserved */
|
|
|
|
/* 0xf8 reserved */
|
1994-05-24 10:09:53 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* The instruction data structure.
|
|
|
|
*/
|
|
|
|
struct bpf_insn {
|
1996-08-19 20:28:25 +00:00
|
|
|
u_short code;
|
|
|
|
u_char jt;
|
|
|
|
u_char jf;
|
|
|
|
bpf_u_int32 k;
|
1994-05-24 10:09:53 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 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 }
|
|
|
|
|
2003-01-20 19:08:46 +00:00
|
|
|
/*
|
|
|
|
* Structure to retrieve available DLTs for the interface.
|
|
|
|
*/
|
|
|
|
struct bpf_dltlist {
|
|
|
|
u_int bfl_len; /* number of bfd_list array */
|
|
|
|
u_int *bfl_list; /* array of DLTs */
|
|
|
|
};
|
|
|
|
|
1999-12-29 04:46:21 +00:00
|
|
|
#ifdef _KERNEL
|
Introduce support for zero-copy BPF buffering, which reduces the
overhead of packet capture by allowing a user process to directly "loan"
buffer memory to the kernel rather than using read(2) to explicitly copy
data from kernel address space.
The user process will issue new BPF ioctls to set the shared memory
buffer mode and provide pointers to buffers and their size. The kernel
then wires and maps the pages into kernel address space using sf_buf(9),
which on supporting architectures will use the direct map region. The
current "buffered" access mode remains the default, and support for
zero-copy buffers must, for the time being, be explicitly enabled using
a sysctl for the kernel to accept requests to use it.
The kernel and user process synchronize use of the buffers with atomic
operations, avoiding the need for system calls under load; the user
process may use select()/poll()/kqueue() to manage blocking while
waiting for network data if the user process is able to consume data
faster than the kernel generates it. Patchs to libpcap are available
to allow libpcap applications to transparently take advantage of this
support. Detailed information on the new API may be found in bpf(4),
including specific atomic operations and memory barriers required to
synchronize buffer use safely.
These changes modify the base BPF implementation to (roughly) abstrac
the current buffer model, allowing the new shared memory model to be
added, and add new monitoring statistics for netstat to print. The
implementation, with the exception of some monitoring hanges that break
the netstat monitoring ABI for BPF, will be MFC'd.
Zerocopy bpf buffers are still considered experimental are disabled
by default. To experiment with this new facility, adjust the
net.bpf.zerocopy_enable sysctl variable to 1.
Changes to libpcap will be made available as a patch for the time being,
and further refinements to the implementation are expected.
Sponsored by: Seccuris Inc.
In collaboration with: rwatson
Tested by: pwood, gallatin
MFC after: 4 months [1]
[1] Certain portions will probably not be MFCed, specifically things
that can break the monitoring ABI.
2008-03-24 13:49:17 +00:00
|
|
|
#ifdef MALLOC_DECLARE
|
|
|
|
MALLOC_DECLARE(M_BPF);
|
|
|
|
#endif
|
|
|
|
#ifdef SYSCTL_DECL
|
|
|
|
SYSCTL_DECL(_net_bpf);
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Rotate the packet buffers in descriptor d. Move the store buffer into the
|
|
|
|
* hold slot, and the free buffer ino the store slot. Zero the length of the
|
2012-12-10 16:14:44 +00:00
|
|
|
* new store buffer. Descriptor lock should be held. Hold buffer must
|
|
|
|
* not be marked "in use".
|
Introduce support for zero-copy BPF buffering, which reduces the
overhead of packet capture by allowing a user process to directly "loan"
buffer memory to the kernel rather than using read(2) to explicitly copy
data from kernel address space.
The user process will issue new BPF ioctls to set the shared memory
buffer mode and provide pointers to buffers and their size. The kernel
then wires and maps the pages into kernel address space using sf_buf(9),
which on supporting architectures will use the direct map region. The
current "buffered" access mode remains the default, and support for
zero-copy buffers must, for the time being, be explicitly enabled using
a sysctl for the kernel to accept requests to use it.
The kernel and user process synchronize use of the buffers with atomic
operations, avoiding the need for system calls under load; the user
process may use select()/poll()/kqueue() to manage blocking while
waiting for network data if the user process is able to consume data
faster than the kernel generates it. Patchs to libpcap are available
to allow libpcap applications to transparently take advantage of this
support. Detailed information on the new API may be found in bpf(4),
including specific atomic operations and memory barriers required to
synchronize buffer use safely.
These changes modify the base BPF implementation to (roughly) abstrac
the current buffer model, allowing the new shared memory model to be
added, and add new monitoring statistics for netstat to print. The
implementation, with the exception of some monitoring hanges that break
the netstat monitoring ABI for BPF, will be MFC'd.
Zerocopy bpf buffers are still considered experimental are disabled
by default. To experiment with this new facility, adjust the
net.bpf.zerocopy_enable sysctl variable to 1.
Changes to libpcap will be made available as a patch for the time being,
and further refinements to the implementation are expected.
Sponsored by: Seccuris Inc.
In collaboration with: rwatson
Tested by: pwood, gallatin
MFC after: 4 months [1]
[1] Certain portions will probably not be MFCed, specifically things
that can break the monitoring ABI.
2008-03-24 13:49:17 +00:00
|
|
|
*/
|
|
|
|
#define ROTATE_BUFFERS(d) do { \
|
|
|
|
(d)->bd_hbuf = (d)->bd_sbuf; \
|
|
|
|
(d)->bd_hlen = (d)->bd_slen; \
|
|
|
|
(d)->bd_sbuf = (d)->bd_fbuf; \
|
|
|
|
(d)->bd_slen = 0; \
|
|
|
|
(d)->bd_fbuf = NULL; \
|
|
|
|
bpf_bufheld(d); \
|
|
|
|
} while (0)
|
|
|
|
|
2006-06-02 19:59:33 +00:00
|
|
|
/*
|
|
|
|
* Descriptor associated with each attached hardware interface.
|
2012-04-06 06:53:58 +00:00
|
|
|
* FIXME: this structure is exposed to external callers to speed up
|
|
|
|
* bpf_peers_present() call. However we cover all fields not needed by
|
|
|
|
* this function via BPF_INTERNAL define
|
2006-06-02 19:59:33 +00:00
|
|
|
*/
|
|
|
|
struct bpf_if {
|
|
|
|
LIST_ENTRY(bpf_if) bif_next; /* list of all interfaces */
|
|
|
|
LIST_HEAD(, bpf_d) bif_dlist; /* descriptor list */
|
2012-04-06 06:53:58 +00:00
|
|
|
#ifdef BPF_INTERNAL
|
2006-06-02 19:59:33 +00:00
|
|
|
u_int bif_dlt; /* link layer type */
|
Implement flexible BPF timestamping framework.
- Allow setting format, resolution and accuracy of BPF time stamps per
listener. Previously, we were only able to use microtime(9). Now we can
set various resolutions and accuracies with ioctl(2) BIOCSTSTAMP command.
Similarly, we can get the current resolution and accuracy with BIOCGTSTAMP
command. Document all supported options in bpf(4) and their uses.
- Introduce new time stamp 'struct bpf_ts' and header 'struct bpf_xhdr'.
The new time stamp has both 64-bit second and fractional parts. bpf_xhdr
has this time stamp instead of 'struct timeval' for bh_tstamp. The new
structures let us use bh_tstamp of same size on both 32-bit and 64-bit
platforms without adding additional shims for 32-bit binaries. On 64-bit
platforms, size of BPF header does not change compared to bpf_hdr as its
members are already all 64-bit long. On 32-bit platforms, the size may
increase by 8 bytes. For backward compatibility, struct bpf_hdr with
struct timeval is still the default header unless new time stamp format is
explicitly requested. However, the behaviour may change in the future and
all relevant code is wrapped around "#ifdef BURN_BRIDGES" for now.
- Add experimental support for tagging mbufs with time stamps from a lower
layer, e.g., device driver. Currently, mbuf_tags(9) is used to tag mbufs.
The time stamps must be uptime in 'struct bintime' format as binuptime(9)
and getbinuptime(9) do.
Reviewed by: net@
2010-06-15 19:28:44 +00:00
|
|
|
u_int bif_hdrlen; /* length of link header */
|
2006-06-02 19:59:33 +00:00
|
|
|
struct ifnet *bif_ifp; /* corresponding interface */
|
2012-04-06 06:53:58 +00:00
|
|
|
struct rwlock bif_lock; /* interface lock */
|
2012-04-06 06:55:21 +00:00
|
|
|
LIST_HEAD(, bpf_d) bif_wlist; /* writer-only list */
|
2012-05-21 22:17:29 +00:00
|
|
|
int flags; /* Interface flags */
|
2012-04-06 06:53:58 +00:00
|
|
|
#endif
|
2006-06-02 19:59:33 +00:00
|
|
|
};
|
|
|
|
|
Introduce support for zero-copy BPF buffering, which reduces the
overhead of packet capture by allowing a user process to directly "loan"
buffer memory to the kernel rather than using read(2) to explicitly copy
data from kernel address space.
The user process will issue new BPF ioctls to set the shared memory
buffer mode and provide pointers to buffers and their size. The kernel
then wires and maps the pages into kernel address space using sf_buf(9),
which on supporting architectures will use the direct map region. The
current "buffered" access mode remains the default, and support for
zero-copy buffers must, for the time being, be explicitly enabled using
a sysctl for the kernel to accept requests to use it.
The kernel and user process synchronize use of the buffers with atomic
operations, avoiding the need for system calls under load; the user
process may use select()/poll()/kqueue() to manage blocking while
waiting for network data if the user process is able to consume data
faster than the kernel generates it. Patchs to libpcap are available
to allow libpcap applications to transparently take advantage of this
support. Detailed information on the new API may be found in bpf(4),
including specific atomic operations and memory barriers required to
synchronize buffer use safely.
These changes modify the base BPF implementation to (roughly) abstrac
the current buffer model, allowing the new shared memory model to be
added, and add new monitoring statistics for netstat to print. The
implementation, with the exception of some monitoring hanges that break
the netstat monitoring ABI for BPF, will be MFC'd.
Zerocopy bpf buffers are still considered experimental are disabled
by default. To experiment with this new facility, adjust the
net.bpf.zerocopy_enable sysctl variable to 1.
Changes to libpcap will be made available as a patch for the time being,
and further refinements to the implementation are expected.
Sponsored by: Seccuris Inc.
In collaboration with: rwatson
Tested by: pwood, gallatin
MFC after: 4 months [1]
[1] Certain portions will probably not be MFCed, specifically things
that can break the monitoring ABI.
2008-03-24 13:49:17 +00:00
|
|
|
void bpf_bufheld(struct bpf_d *d);
|
2002-03-19 21:54:18 +00:00
|
|
|
int bpf_validate(const struct bpf_insn *, int);
|
2002-11-14 23:24:13 +00:00
|
|
|
void bpf_tap(struct bpf_if *, u_char *, u_int);
|
|
|
|
void bpf_mtap(struct bpf_if *, struct mbuf *);
|
2003-12-28 03:56:00 +00:00
|
|
|
void bpf_mtap2(struct bpf_if *, void *, u_int, struct mbuf *);
|
2002-03-19 21:54:18 +00:00
|
|
|
void bpfattach(struct ifnet *, u_int, u_int);
|
2002-11-14 23:24:13 +00:00
|
|
|
void bpfattach2(struct ifnet *, u_int, u_int, struct bpf_if **);
|
2002-03-19 21:54:18 +00:00
|
|
|
void bpfdetach(struct ifnet *);
|
The advent of if_detach, allowing interface removal at runtime, makes it
possible for a panic to occur if BPF is in use on the interface at the
time of the call to if_detach. This happens because BPF maintains pointers
to the struct ifnet describing the interface, which is freed by if_detach.
To correct this problem, a new call, bpfdetach, is introduced. bpfdetach
locates BPF descriptor references to the interface, and NULLs them. Other
BPF code is modified so that discovery of a NULL interface results in
ENXIO (already implemented for some calls). Processes blocked on a BPF
call will also be woken up so that they can receive ENXIO.
Interface drivers that invoke bpfattach and if_detach must be modified to
also call bpfattach(ifp) before calling if_detach(ifp). This is relevant
for buses that support hot removal, such as pccard and usb. Patches to
all effected devices will not be committed, only to if_wi.c, due to
testing limitations. To reproduce the crash, load up tcpdump on you
favorite pccard ethernet card, and then eject the card. As some pccard
drivers do not invoke if_detach(ifp), this bug will not manifest itself
for those drivers.
Reviewed by: wes
2000-03-19 05:42:34 +00:00
|
|
|
|
2002-03-19 21:54:18 +00:00
|
|
|
void bpfilterattach(int);
|
2008-08-26 16:12:49 +00:00
|
|
|
u_int bpf_filter(const struct bpf_insn *, u_char *, u_int, u_int);
|
2002-11-14 23:24:13 +00:00
|
|
|
|
2006-06-02 19:59:33 +00:00
|
|
|
static __inline int
|
|
|
|
bpf_peers_present(struct bpf_if *bpf)
|
|
|
|
{
|
|
|
|
|
2006-06-14 02:23:28 +00:00
|
|
|
if (!LIST_EMPTY(&bpf->bif_dlist))
|
2006-06-03 18:48:14 +00:00
|
|
|
return (1);
|
2006-06-03 06:37:00 +00:00
|
|
|
return (0);
|
2006-06-02 19:59:33 +00:00
|
|
|
}
|
|
|
|
|
2002-11-14 23:24:13 +00:00
|
|
|
#define BPF_TAP(_ifp,_pkt,_pktlen) do { \
|
2006-06-02 19:59:33 +00:00
|
|
|
if (bpf_peers_present((_ifp)->if_bpf)) \
|
2002-11-14 23:24:13 +00:00
|
|
|
bpf_tap((_ifp)->if_bpf, (_pkt), (_pktlen)); \
|
|
|
|
} while (0)
|
|
|
|
#define BPF_MTAP(_ifp,_m) do { \
|
2006-06-02 19:59:33 +00:00
|
|
|
if (bpf_peers_present((_ifp)->if_bpf)) { \
|
2003-12-28 03:56:00 +00:00
|
|
|
M_ASSERTVALID(_m); \
|
2002-11-14 23:24:13 +00:00
|
|
|
bpf_mtap((_ifp)->if_bpf, (_m)); \
|
2003-12-28 03:56:00 +00:00
|
|
|
} \
|
|
|
|
} while (0)
|
|
|
|
#define BPF_MTAP2(_ifp,_data,_dlen,_m) do { \
|
2006-06-02 19:59:33 +00:00
|
|
|
if (bpf_peers_present((_ifp)->if_bpf)) { \
|
2003-12-28 03:56:00 +00:00
|
|
|
M_ASSERTVALID(_m); \
|
|
|
|
bpf_mtap2((_ifp)->if_bpf,(_data),(_dlen),(_m)); \
|
|
|
|
} \
|
2002-11-14 23:24:13 +00:00
|
|
|
} while (0)
|
1994-05-24 10:09:53 +00:00
|
|
|
#endif
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Number of scratch memory words (for BPF_LD|BPF_MEM and BPF_ST).
|
|
|
|
*/
|
|
|
|
#define BPF_MEMWORDS 16
|
|
|
|
|
2013-10-28 20:32:05 +00:00
|
|
|
#ifdef _SYS_EVENTHANDLER_H_
|
2013-10-28 07:45:03 +00:00
|
|
|
/* BPF attach/detach events */
|
|
|
|
struct ifnet;
|
|
|
|
typedef void (*bpf_track_fn)(void *, struct ifnet *, int /* dlt */,
|
|
|
|
int /* 1 =>'s attach */);
|
|
|
|
EVENTHANDLER_DECLARE(bpf_track, bpf_track_fn);
|
2013-10-28 20:32:05 +00:00
|
|
|
#endif /* _SYS_EVENTHANDLER_H_ */
|
2013-10-28 07:45:03 +00:00
|
|
|
|
2002-11-14 23:24:13 +00:00
|
|
|
#endif /* _NET_BPF_H_ */
|