TRACEPKTDUMP(1)
π TRACEPKTDUMP(1) π
okay so bestie, we're in section 1 of the User Commands manual, and today's main character is tracepktdump. she's literally the friend who translates packet gibberish into something your eyeballs can actually read. no cap. π
πΈ NAME πΈ
tracepktdump β output packets in human readable format π¦
β¨ SYNOPSIS β¨
tracepktdump [ -f exp | --filter=exp ] [ -c num | --count=num ] inputuri ...
like, you hand her one or more inputuri things and she goes off. that's the whole vibe. π
π DESCRPTION π
(yes, that's how the heading is spelled in here, we don't make the rules, we just respect the original π)
tracepktdump verbosely outputs packets in a human readable form, suitable for diagnosing packets. like, she's not subtle, she's not quiet, she's telling you everything about those packets because that's the whole point β you're diagnosing. π
tracepktdump uses the libpacketdump library. and ooh, there's an example tracepktdump program in the examples directory that shows how to use libpacketdump β so if you wanna peek at how the sausage gets made, that's your spot. πβ¨
now the flags, bestie:
-fbpf-filter /--filterbpf-filter β output only packets that match the bpf-filter expression. so like, filter down to just the packets you care about. and if you're sitting there going "what even is bpf-filter syntax", go readtcpdump(1), she explains it. π-cnum /--countnum β stop after displaying num packets. because sometimes you only want a little taste, not the whole buffet. π
fr fr,-f expand--filter=expare the same energy in the synopsis, just spelled a lil differently. don't come for her. π«Ά
π LINKS π
More details about tracepktdump (and libtrace) can be found at http://www.wand.net.nz/trac/libtrace/wiki/UserDocumentation β go click, it's giving documentation, it's giving lore. π
π SEE ALSO π
the whole friend group, and they all ate:
libtrace(3)tracemerge(1)tracesplit(1)tracesplit_dir(1)tracefilter(1)tracestats(1)tracesummary(1)traceconvert(1)tracereport(1)tracertstats(1)traceanon(1)tracereplay(1)tracediff(1)traceends(1)tracetopends(1)
π AUTHORS π
Perry Lorier <perry@cs.waikato.ac.nz>, Daniel Lawson <dlawson@cs.waikato.ac.nz> β icons, both of them. they built the thing. show some respect. π
and that's the page, bestie!! π this lil slice of tracepktdump comes to you from libtrace, dated November 2005, and it lives at home as TRACEPKTDUMP(1). stay nosy, stay diagnosing, mwah π
ππ§
π¦ where this page comes from
- debian bookworm: libtrace-tools 3.0.22-0.1
- debian trixie: libtrace-tools 3.0.22-0.2
- ubuntu jammy: libtrace-tools 3.0.21-1ubuntu5
- ubuntu noble: libtrace-tools 3.0.22-0.2build1
- ubuntu questing: libtrace-tools 3.0.22-0.2build1
- ubuntu resolute: libtrace-tools 3.0.22-0.2build2
- ubuntu stonking: libtrace-tools 3.0.22-0.2build2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms