←back to thread

Trippy – A Network Diagnostic Tool

(trippy.cli.rs)
265 points night-rider | 4 comments | 10 Dec 23 03:46 UTC | HN request time: 0.705s | source
1. FujiApple ◴[10 Dec 23 04:43 UTC] No.38589140[source]▶
Author here, thanks for posting this (i’d meant to do a show HN post at some point).

Trippy is a modern, cross platform, feature rich alternative to MTR with a fancy TUI. And yes, it’s written in Rust.

https://github.com/fujiapple852/trippy

replies(2): >>38590955 #>>38593281 #
2. spacecadet ◴[10 Dec 23 11:57 UTC] No.38590955[source]▶
Super cool, inspiring me to finish my rust book...
3. booboofixer ◴[10 Dec 23 17:45 UTC] No.38593281[source]▶
Wondering if you took a look at or took some inspiration from the packet structures for TWAMP/TWAMP-LITE/SDLM RFCs for round trip times/packet loss measurements or if you sort of winged it and came up with your own. I've been meaning to learn rust by implementing those protocols.
replies(1): >>38596595 #
4. FujiApple ◴[11 Dec 23 01:06 UTC] No.38596595[source]▶
For the RTT and loss% measurements Trippy just does the obvious thing (i.e. RTT = recv time - send time and loss% = lost / total_sent).

There is a plan [0] to add custom columns to Trippy and then to add various jitter measurements [1].

Thanks for pointing out the above RFCs, I'll take a look at those and see if they make sense to add to Trippy.

[0] https://github.com/fujiapple852/trippy/issues/757

[1] https://github.com/fujiapple852/trippy/issues/39