mtr
trippy
mtr | trippy | |
---|---|---|
22 | 18 | |
2,537 | 3,019 | |
- | - | |
6.3 | 9.8 | |
about 2 months ago | 3 days ago | |
C | Rust | |
GNU General Public License v3.0 only | 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.
mtr
-
Trippy 0.9.0 Release
As a reminder, Trippy combines the functionality of traceroute and ping and is designed to assist with the analysis of networking issues. You can think of it as a modern, cross platform, Rust based version of tools such as mtr, with a bunch of advanced features and a fancy TUI.
-
Show HN: How did YOUR computer reach my server?
Cool project! Two suggestions, one serious, one frivolous:
- I wonder if you could get more accurate results by using TCP or UDP instead of ICMP. I think traditional traceroute has an option to use UDP, mtr [1] can use TCP or UDP, and tcptraceroute [2] can use TCP.
- This would be a perfect fit for some Talking Heads references. "And you may ask yourself, well, how did I get here?" [3]
[1] https://github.com/traviscross/mtr
[2] https://linux.die.net/man/1/tcptraceroute
[3] https://en.wikipedia.org/wiki/Once_in_a_Lifetime_(Talking_He...
- MTR Traceroute
-
Internet goes out every day at 4:15pm
Run mtr, or whatever the Windows equivalent might be, and leave it running shortly before 4:15pm, and see where the traffic stops when the Internet shuts off.
-
What software/tools should every sysadmin have on their desktop?
Lot of great stuff here, haven’t seen MTR yet: https://github.com/traviscross/mtr
-
Troubleshooting Issues
Consider using MTR (software) towards the actual end-point of the SIP connection to get a combination of traceroute and ping which will be much more revealing. This will also allow you to quickly identify if the problem is local to your equipment or somewhere along the path. Consider allowing her to join a Google Conference from Teams to determine if it is provider related. Yes, port mirroring and wire shark is the gold standard and will display the "answer" on your screen quickly but it requires skills to know what to analyze, look at and how to interpret the data.
- ICMP, Ping, and Traceroute – What I Wish I Was Taught
-
Tmux over ssh freezes faster then ssh session timeout
Have you tried something like mtr to check for connection issues? I would recommand the view you get when hitting d twice after starting it (with the colored graph for latencies).
-
What's everyone working on this week (17/2022)?
Continuing to build trippy; a network diagnostic tool inspired by mtr. There is still a long way to go but it is getting closer to feature parity with mtr.
- Internet magically gets faster when opening speedtest?
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?
Wireshark - Read-only mirror of Wireshark's Git repository at https://gitlab.com/wireshark/wireshark. ⚠️ GitHub won't let us disable pull requests. ⚠️ THEY WILL BE IGNORED HERE ⚠️ Upload them at GitLab instead.
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.
iperf - iperf3: A TCP, UDP, and SCTP network bandwidth measurement tool
pingapi - Ping API for piracy.moe
mitmproxy - An interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers.
bongo - A cross-platform MongoDB dashboard CLI Viewer
perf-tools - Performance analysis tools based on Linux perf_events (aka perf) and ftrace
weaver - API tool,but egui style and rusty
httpstat - curl statistics made simple
pyroscope-rs - Pyroscope Profiler for Rust. Profile your Rust applications.
Sysdig - Linux system exploration and troubleshooting tool with first class support for containers
DIIS-rs - Minimal Rust library for the Direct Inversion in the Iterative Subspace (DIIS) algorithm and its variants