violin
trippy
| violin | trippy | |
|---|---|---|
| 1 | 18 | |
| 20 | 3,030 | |
| - | - | |
| 3.9 | 9.8 | |
| 11 months ago | 1 day ago | |
| Rust | Rust | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
violin
-
Network Coordinates
In my Rust Vivaldi implementation (called violin), a single calculation of two 8D coordinates using stack memory on my 8 core AMD Ryzen 7 5850U laptop with 16GB RAM takes ~16.5ns. A benchmark of 1,000,000 calculations takes 16.5ms.
trippy
-
Apnic: Cgnat is harming internet innovation (2022)
[3] https://github.com/fujiapple852/trippy/issues/1104
- FLaNK Stack Weekly 11 Dec 2023
-
Trippy – A Network Diagnostic Tool
You are right that showing packet loss for intermediate hops is a frequent source of confusion.
Rather than leave it out, I added a status column which shows different statuses for intermediate hops (blue if the hop responds to less than 100% of probes and brown if it responds to 0%) vs the target hop (amber and red).
Where this breaks down is when dealing with ECMP for UDP & TCP tracing, as a given hop (ttl) may represent the target for a given round of tracing but not for the next. The mistake, imho, is to associate _any_ data with a hop (ttl) rather than the hop in the context of a tracing flow.
That is why Trippy had a number of features aimed at helping with ECMP, such as Paris and Dublin tracing, and the ability to filter tracing by unique flow id. I've covered these quite a bit in the 0.8.0 [0] and 0.9.0 [1] release notes if you want to know more.
[0] https://github.com/fujiapple852/trippy/releases/tag/0.8.0
- Trippy: A Network Diagnostic Tool
- Trippy: Network Diagnostic Tool
-
Trippy 0.9.0 Release
Tracing flows: breakdown complex UDP/TCP ECMP traces into individual flows (i.e. common network path); render a chart of flows in GraphViz DOT format (example)
-
[Media] Introducing Trippy: A Network Diagnostic Tool
u/queiss_ the 0.8.0 release note has a section covering this, but the TL;DR is:
What are some alternatives?
RustHound - Active Directory data collector for BloodHound written in Rust. 🦀
mtr - Official repository for mtr, a network diagnostic tool
sniffnet - Comfortably monitor your Internet traffic 🕵️♂️
mezura - A fairly fast, fairly accurate and very customizable stats generator and growth tracker, for programming projects, in the form of a CLI executable, written in Rust.
rathole - A lightweight and high-performance reverse proxy for NAT traversal, written in Rust. An alternative to frp and ngrok.
pingapi - Ping API for piracy.moe
bongo - A cross-platform MongoDB dashboard CLI Viewer
weaver - API tool,but egui style and rusty
pyroscope-rs - Pyroscope Profiler for Rust. Profile your Rust applications.
DIIS-rs - Minimal Rust library for the Direct Inversion in the Iterative Subspace (DIIS) algorithm and its variants
joshuto - ranger-like terminal file manager written in Rust
ratatui - Rust library that's all about cooking up terminal user interfaces (TUIs) 👨🍳🐀