TRACEDIFF(1)
π tracediff(1) β find and print differences between two traces π
okay bestie, listen up β this is tracediff, a User Commands girlie who lives in section 1 of the manual and whose whole entire personality is comparing two trace files and telling you exactly what's different. no cap. β¨
β¨ NAME β¨
tracediff β find and print differences between two traces π¦
πΈ SYNOPSIS πΈ
tracediff [ -m maxdiff ] firsturi seconduri
π DESCRIPTION π
so basically, tracediff takes two trace files and compares them, then prints out all the deets of the packets that differ straight to standard output. it's giving detective energy. π
when is this useful, you ask? iconic question:
- finding packets that are in one trace but not in the other π
- finding conversion errors
- finding snapping errors
lowkey it's the vibe check your traces never asked for, and honestly? they needed it. π
-m maxdiffβ stop processing after displayingmaxdiffdifferences. that's it, that's the flag. once it's shown you that many diffs, it's done, it's clocking out, main character has left the building. πͺβ¨
π EXAMPLES π
here's the moment you've been waiting for, fr fr:
tracediff -m 10 erf:/traces/orig.erf.gz pcapfile:/traces/convert.pcap.gz
ten differences max, two trace URIs, one slay. π«Ά
π BUGS π
okay so not exactly a bug, but bestie you need to know: the contents of the framing headers (i.e. the PCAP or ERF encapsulation) are not compared. so if the wrapper is different but the packets match... tracediff is not gonna clock it. π
π LINKS π
more details about tracediff (and libtrace) can be found at:
http://www.wand.net.nz/trac/libtrace/wiki/UserDocumentation
go read it, it's giving documentation realness πβ¨
π SEE ALSO π
the whole friend group, assembled:
libtrace(3)tracemerge(1)tracefilter(1)traceconvert(1)tracestats(1)tracesummary(1)tracertstats(1)tracesplit(1)tracesplit_dir(1)tracereport(1)tracepktdump(1)traceanon(1)tracereplay(1)traceends(1)tracetopends(1)
collect them all, they're literally the avengers of packet tooling. π¦π
π«Ά AUTHORS π«Ά
Shane Alcock β <salcock@cs.waikato.ac.nz> πΈ
and that's the whole page, bestie!! this lil masterpiece is from tracediff (libtrace), dated January 2010 β yes, it's vintage, and yes, it still ate. π β¨ π
π¦ 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