TRACEENDS(1)

💫 TRACEENDS 💫

okay bestie, welcome to the traceends manual page, section 1 of the User Commands girlies. this is the little tool that summarises all the traffic every single endpoint in your trace got up to. let's get into it 🫶

---

✨ NAME ✨

traceends — summarise traffic done by every endpoint observed in a trace

---

🌸 SYNOPSIS 🌸

tracetopends [ -f bpf | --filter=bpf] [ -a addrtype |
--address=addrtype] [ -H | --help]

inputuri [inputuri ...]

not me spotting that the synopsis says tracetopends and not traceends 😭 that's literally what the page says so i'm keeping it exactly as-is, no cap. traceends, tracetopends, they're siblings, it's giving family drama.

---

💖 DESCRIPTION 💖

traceends reports the number of bytes and packets sent and received by each endpoint observed in the input trace(s). it's the receipts for every single address in your capture, fr fr.

usually, you don't want to run this program directly — see tracetopends instead. it's giving "i'm the understudy, the main character is over there" ✨

• -f bpf filter — output only packets that match tcpdump style bpf filter
• -A address type — Specifies how an endpoint should be defined. Suitable options are "mac", "v4" and "v6" which will report endpoint stats for each observed MAC address, IPv4 address and IPv6 address respectively.

heads up: the synopsis writes these as -f/--filter=bpf and -a/--address=addrtype, and the description body writes them as -f and -A. that's just how the original rolls, and we don't editorialise 💅

---

👑 OUTPUT 👑

Output is written to stdout in columns separated by blank space. yes bestie, blank space, not commas, not tabs, just vibes and whitespace 🌈

The columns are (in order):

• Endpoint address
• Time last observed
• Packets originating from the endpoint
• Bytes originating from the endpoint (IP header onwards)
• Payload originating from the endpoint (post transport header)
• Packets sent to the endpoint
• Bytes sent to the endpoint (IP header onwards)
• Payload sent to the endpoint (post transport header)

---

🦋 EXAMPLES 🦋

Get stats for each individual MAC address in a trace:

traceends -a mac erf:trace.erf.gz

ate, no notes 🍓

---

🎀 LINKS 🎀

More details about traceends (and libtrace) can be found at

http://www.wand.net.nz/trac/libtrace/wiki/UserDocumentation

---

🌟 SEE ALSO 🌟

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

like, the whole friend group showed up 💜

---

🌈 AUTHORS 🌈

Shane Alcock <salcock@cs.waikato.ac.nz>

---

and that's the whole page, bestie!! this one's from traceends (libtrace), dated September 2011 — yes she's a 2011 icon and she still eats 👑 periodt 💅