opapacketcapture(1)

opapacketcapture1

Usage

opapacketcapture [-o outfile] [-d devfile] [-f filterfile] [-t triggerfile] [-l triggerlag] [-a alarm] [-p packets] [-s maxblocks] [-v [-v]]

Options

--help

Produces full help text.

-o outfile

Specifies the output file for captured packets.
Default is packetDump.pcap

-d devfile

Specifies the device file for capturing packets.

-f filterfile

Specifies the file used for filtering. If absent, no filtering is done.

-t triggerfile

Specifies the file used for triggering a stop capture. If absent, normal triggering is performed.

-l triggerlag

Specifies the number of packets to collect after trigger condition is met, before dumping data and exiting. Default is 10.

-a alarm

Specifies the number of seconds for alarm trigger to dump capture and exit.

-p packets

Specifies the number of packets for alarm trigger to dump capture and exit.

-s maxblocks

Specifies the number of blocks to allocate for ring buffer. Value is in Millions. Default is 2 which corresponds to 128 MiB because 1 block = 64 Bytes.

-v

Produces verbose output. (Use verbose Level 1+ to show levels.)

Examples

# opapacketcapture

opapacketcapture: Capturing packets using 128 MiB buffer

^C

opapacketcapture: Triggered

Number of packets stored is 100

In the example above, opapacketcapture operates until CTRL+C is entered.

Releases

4 releases since Debian 10 (Buster); the text changed 1 time.

  1. 10
  2. 11–13

From opa-basic-tools 10.10.3.0.11-1+b2 in Debian 13 (Trixie). Parsed by carta from the page's man source.