2 The following instructions apply if you have a Linux or FreeBSD platform and
3 want libpcap to support the DAG range of passive network monitoring cards from
4 Endace (http://www.endace.com, see below for further contact details).
6 1) Install and build the DAG software distribution by following the
7 instructions supplied with that package. Current Endace customers can download
8 the DAG software distibution from https://www.endace.com
10 2) Configure libcap. To allow the 'configure' script to locate the DAG
11 software distribution use the '--with-dag' option:
13 ./configure --with-dag=DIR
15 Where DIR is the root of the DAG software distribution, for example
16 /var/src/dag. If the DAG software is correctly detected 'configure' will
19 checking whether we have DAG API... yes
21 If 'configure' reports that there is no DAG API, the directory may have been
22 incorrectly specified or the DAG software was not built before configuring
25 See also the libpcap INSTALL.txt file for further libpcap configuration
28 Building libpcap at this stage will include support for both the native packet
29 capture stream (linux or bpf) and for capturing from DAG cards. To build
30 libpcap with only DAG support specify the capture type as 'dag' when
33 ./configure --with-dag=DIR --with-pcap=dag
35 Applications built with libpcap configured in this way will only detect DAG
36 cards and will not capture from the native OS packet stream.
38 ----------------------------------------------------------------------
40 Libpcap when built for DAG cards against dag-2.5.1 or later releases:
42 Timeouts are supported. pcap_dispatch() will return after to_ms milliseconds
43 regardless of how many packets are received. If to_ms is zero pcap_dispatch()
44 will block waiting for data indefinitely.
46 pcap_dispatch() will block on and process a minimum of 64kB of data (before
47 filtering) for efficiency. This can introduce high latencies on quiet
48 interfaces unless a timeout value is set. The timeout expiring will override
49 the 64kB minimum causing pcap_dispatch() to process any available data and
52 pcap_setnonblock is supported. When nonblock is set, pcap_dispatch() will
53 check once for available data, process any data available up to count, then
56 pcap_findalldevs() is supported, e.g. dag0, dag1...
58 Some DAG cards can provide more than one 'stream' of received data.
59 This can be data from different physical ports, or separated by filtering
60 or load balancing mechanisms. Receive streams have even numbers, e.g.
61 dag0:0, dag0:2 etc. Specifying transmit streams for capture is not supported.
63 pcap_setfilter() is supported, BPF programs run in userspace.
65 pcap_setdirection() is not supported. Only received traffic is captured.
66 DAG cards normally do not have IP or link layer addresses assigned as
67 they are used to passively monitor links.
69 pcap_breakloop() is supported.
71 pcap_datalink() and pcap_list_datalinks() are supported. The DAG card does
72 not attempt to set the correct datalink type automatically where more than
75 pcap_stats() is supported. ps_drop is the number of packets dropped due to
76 RX stream buffer overflow, this count is before filters are applied (it will
77 include packets that would have been dropped by the filter). The RX stream
78 buffer size is user configurable outside libpcap, typically 16-512MB.
80 pcap_get_selectable_fd() is not supported, DAG cards do not support
83 pcap_inject() and pcap_sendpacket() are not supported.
85 ----------------------------------------------------------------------
87 Please submit bug reports via <support@endace.com>.
89 Please also visit our Web site at:
91 http://www.endace.com/
93 For more information about Endace DAG cards contact <sales@endace.com>.