TRACEREPORT(1)

💖 tracereport — the manual page, but make it make sense 💖

okay bestie, so this is tracereport, a User Commands girlie, and she is about to give you the most detailed tea on your packet trace. no cap. ✨

---

🌸 NAME 🌸

tracereport — produce various reports on a trace (or traceset) 💅

---

🎀 SYNOPSIS 🎀

tracereport [ -f bpf | --filter=bpf ] [ -e | --error ] [ -F | --flow ]
[ -m | --misc ] [ -P | --protocol ] [ -p | --port ] [ -T | --tos ] [
-t | --ttl ] [ -O | --tcpoptions ] [ -o | --synoptions ] [ -n |
--nlp ] [ -d | --direction ] [ -C | --ecn ] [ -s | --tcpsegment ]
inputuri...

tracereport -H | --help

so like, you give her one or more inputuri... and a bunch of report options and she just goes. 🦋

---

✨ DESCRIPTION ✨

tracereport can produce a variety of reports on the properties of a trace. the user specifies the reports required using command-line options. that's the whole vibe — you pick the reports, she does the rest. 🌈

• -f bpf-filter, --filter bpf-filter — Only report on packets that match the provided bpf filter. See tcpdump(1) for the syntax of the bpf-filter expression. 👑
• -e, --error — Produce a report on packet errors (e.g checksum failures, rxerrors) 💀
• -F, --flow — Produces a report on the number of flows observed in the trace 🌊
• -m, --misc — Provides a report listing the time of the first packet, and the time of the last packet in the trace, the duration, the total number of packets in the trace, and the average number of packets per second. the lil recap, fr fr ⭐
• -P, --protocol — Produces a report on which transport layer protocols are observed in the trace 🔥
• -p, --port — Produces a report on which port numbers are observed in the trace 🚪
• -T, --tos — Produces a report on the contents of the IP header's ToS field 🎀
• -t, --ttl — Produces a report on the TTL of packets in the trace ⏳
• -O, --tcpoptions — Produces a report on which TCP options are observed on all packets in the trace 🧚
• -o, --synoptions — Produces a report on which combinations of TCP options are observed on SYN packets in the trace 💫
• -n, --nlp — Produces a report on the network layer protocols observed in the trace 🌐
• -d, --direction — Produces a report on how much traffic is travelling in each direction ↔️
• -C, --ecn — Produces a report on the usage of the ECN field of the TCP header 🌸
• -s, --tcpsegment — Produces a report on the sizes of TCP segments in the trace 📏
• -H, --help — Provides usage instructions 🫶

---

🔗 LINKS 🔗

More details about tracereport (and libtrace) can be found at http://www.wand.net.nz/trac/libtrace/wiki/UserDocumentation

---

👀 SEE ALSO 👀

libtrace(3), tracemerge(1), tracesplit(1), tracesplit_dir(1), tracefilter(1), traceconvert(1), tracestats(1), tracertstats(1), tracereport(1), tracepktdump(1), traceanon(1), tracesummary(1), tracereplay(1), tracediff(1), traceends(1), tracetopends(1)

like, the whole libtrace friend group showed up. we love a supportive ensemble. 💜

---

💅 AUTHORS 💅

Perry Lorier <perry@cs.waikato.ac.nz>

---

and that's the whole page bestie — every flag, every report, every reference, untouched and iconic. iykyk 🎀

this was tracereport (libtrace), from October 2006, and it still ate. periodt. 💖✨