BrowseSecurity & networking tools
Trippy
A terminal network diagnostic tool that combines traceroute and ping to help analyze networking issues.
Tested on Linux
Use it
Linux x86_64
You need first
- Needs the network
Download the official 0.13.0 x86_64 musl release tarball from GitHub and install trip into ~/.local/bin
cd /tmp && curl -fsSLO https://github.com/fujiapple852/trippy/releases/download/0.13.0/trippy-0.13.0-x86_64-unknown-linux-musl.tar.gz && mkdir -p trippy-x && tar -xzf trippy-0.13.0-x86_64-unknown-linux-musl.tar.gz -C trippy-x && mkdir -p ~/.local/bin && install -m 755 $(find trippy-x -type f -name trip) ~/.local/bin/trip
Check that it works
trip --versionThe output should contain “trip 0.13.0”.
Run trip <host> in a terminal to start tracing the path to a host; raw socket access may require running it with sudo.
What it does
- Trace the route to a host and ping each hopNot tested
- Set the Type of Service on probe packetsNot tested
- Export trace reports as JSONNot tested
How far pickfit got
Linux x86_64
- Installs
- Starts
- 0 of 3 features work
- Works offline
macOS and Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- trace the network path to a host
- inspect DSCP/ECN QoS treatment of probes along a path
An alternative to mtr, traceroute and ping.
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Installs and starts
- Replayed from scratch
- Works offline
- Checked on 15 Nov 2026
- Version trip 0.13.0
Differences the test machine hit
- README: cargo install trippy --locked / apt install trippy / snap install trippy
In the test: No Rust toolchain or root in this box; I installed the prebuilt GitHub release binary trippy-0.13.0-x86_64-unknown-linux-musl.tar.gz into ~/.local/bin instead (the README mentions precompiled binaries) - README: sudo trip example.com
In the test: Tracing needs root or raw-socket capabilities. Unprivileged mode (-u) failed here because this kernel has no ICMP datagram sockets (/proc/sys/net/ipv4/ping_group_range is missing)