opapacketcapture(1)

💖 NAME 💖

opapacketcapture — bestie, this one starts capturing packet data. That's it, that's the whole job. 👑

So like, it just… sits there, snatching packets, vibing. And when you're done? You stop it with SIGINT or SIGUSR1, and that's what triggers the dump. The program dumps the packets out to a file and exits. Clean, iconic, no notes. ✨

⚠️ Real talk though: using opapacketcapture with large amounts of traffic can cause performance issues on the given host. Intel recommends you use opapacketcapture on hosts with lower packet rates and bandwidth. So don't be the main character on a busy box, okay? 😭 Protect your CPU's peace. 🫶

🌸 Syntax 🌸

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

That's the whole vibe right there. Every flag explained below, no gatekeeping. 💅

✨ Options ✨

• --help — gives you the full help text. Like when you ask your friend to explain the whole situation and they actually do. 🎀
• -o outfile — tells it which output file to write the captured packets into. If you don't say anything, the default is packetDump.pcap. 🍓
• -d devfile — picks the device file used for capturing packets. The little portal where the packets come from. 🌀
• -f filterfile — the file used for filtering. And if you don't pass one at all? No filtering is done. Everything comes through, unfiltered, chaotic, free. 😌
• -t triggerfile — the file used for triggering a stop capture. If it's absent, normal triggering is performed. So either you bring your own trigger or the normal one shows up. 🦋
• -l triggerlag — how many packets to collect after the trigger condition is met, before it dumps the data and dips out. Default is 10. 🧚
• -a alarm — how many seconds for the alarm trigger to dump the capture and exit. ⏰
• -p packets — how many packets for the alarm trigger to dump the capture and exit. 🔢
• -s maxblocks — how many blocks to allocate for the ring buffer. Heads up, the value is in Millions. Default is 2, which corresponds to 128 MiB, because 1 block = 64 Bytes. Math girlies, rise. 🔥
• -v — produces verbose output. (Use verbose Level 1+ to show levels.) Stack it, bestie — -v -v is right there in the syntax. 👀

🌈 Example 🌈

# opapacketcapture

opapacketcapture: Capturing packets using 128 MiB buffer

^C

opapacketcapture: Triggered

Number of packets stored is 100

So in the example above, opapacketcapture just operates along, living its life, until CTRL+C is entered. Then boom — triggered, dump, done. 💀✨

Okay that's the whole page, you're so welcome, this is literally your page now. 💜

Sending you off with the receipts, bestie: this beauty lives in the IFSFFCLIRG manual pages, it's opapacketcapture(1), and the copyright line reads Copyright(C) 2015-2019, Intel Corporation. 🎀🫶 Slay responsibly. 🌟