• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..24-Aug-2021-

README.dump.mdH A D24-Aug-20211.4 KiB2924

daq_dump.cH A D24-Aug-202114.3 KiB473369

libdaq_static_dump.pc.inH A D24-Aug-2021315 1613

README.dump.md

1Dump Module
2===========
3
4A wrapper DAQ module that presents the configuration stack as inline-interface-
5and injection-capable.  All packet messages that are finalized with a passing
6verdict (PASS, REPLACE, WHITELIST, IGNORE) or injected will be written to a PCAP
7savefile.  By default, the packet capture file will be named 'inline-out.pcap'
8in the current directory.  The default filename can be overridden with the
9'file' variable.  For historical reasons, the 'output' variable also exists and
10accepts only one valid argument in 'none' to disable writing out a PCAP file
11altogether.
12
13The Dump DAQ module also supports capturing received packets to a separate PCAP
14savefile.  This is disabled by default, but can be enabled with the 'dump-rx'
15variable.  The 'dump-rx' variable takes an optional argument for the filename
16to dump received packets to; it defaults to 'inline-in.pcap' if no argument is
17given.
18
19When running with multiple instances, the both the TX and RX output filenames
20will be mangled to start with the instance ID followed by an underscore.  For
21example, the default TX output filename would be '2_inline-out.pcap' for the
22second instance.  Both the TX and RX output filenames must be bare (no directory
23structure, relative nor absolute) in such a configuration.
24
25Requirements
26------------
27* libpcap >= 1.0.0
28    (LibPCAP 1.9.0 is available at the time of writing and is recommended.)
29