5 ms·
I wish MTR (My Traceroute) was standard in all operating systems. It offers a number of benefits over Traceroute. MTR essentially combines the functionalities
by Chihuahua0633 2y ago
I wish MTR (My Traceroute) was standard in all operating systems. It offers a number of benefits over Traceroute. MTR essentially combines the functionalities of traceroute and ping, providing a more comprehensive and dynamic view of network paths and performance.
MTR runs continuously, gathering real-time stats that reveal both packet loss and latency trends over time. MTR provides minimum, average, and maximum response times, plus the standard deviation. This is especially useful for troubleshooting intermittent issues or spotting latency spikes.
Of course, MTR isn’t perfect and still faces some of the same challenges as traceroute, like dealing with ICMP rate-limiting, load-balanced paths, or certain network setups that obscure hops. But overall, it provides a richer, more nuanced view, making it a preferred tool for network diagnostics and troubleshooting.
- belfalas 2y agoPlus one for MTR, it’s a great tool. Not perfect, but great.
- 1xdevnet 2y agoAs long as you're the only one doing the troubleshooting, sure. FTA: > The example given is that a handful of users running MTR (do not get me started on this bastard program) can actually hit this rate limit. This is an outstanding example because I have seen something similar in practice. > Consider what that would look like, and how common it would be: If you have a NOC full of people who think they know what they're doing, but don't, that only enhances the probability that everyone is trying to troubleshoot on their own instead of doing a screenshare and coordinating their efforts - thus, you have six guys running MTR to the same IP.
- sneak 2y agoMTR does none of the things you claim it does, which is directly addressed in the article. It certainly claims to, and displays figures as if it could, but it cannot. Even pinging the router IPs directly does not tell you your latency or packet loss to the router, for the reasons explained in the article. mtr is built on false pretenses.
- commandersaki 2y agoThank you, combining ping & traceroute into one tool is a fools errand; keep them separate. Ping to approximate RTT & detect loss between endpoints. Traceroute to approximate forward path of a packet to destination. Combining both gets you crap like a washing & dryer combo machine where it does both neither well.
- red-iron-pine 2y agoMTR is great... if you know what route you expect it to take, and expect it to take back. Very useful for troubleshooting inside of the Enterprise, or when I did a lot of ISP work. MTR to some rando website in a different timezone could be useful... but not often.