MTR

mtr combines the functionality of the 'traceroute' and 'ping' programs in a single network diagnostic tool. As mtr starts, it investigates the network connection between the host mtr runs on and a user-specified destination host. It sends probes to the destination with successively larger time-to-live values, and uses the responses from intervening routers to discover and measure the path. As it does this, it prints running statistics for each hop. Intermediate routers may be configured to never send these ICMP responses, or may rate-limit them, so apparent loss at an intermediate hop does not always mean that forwarded traffic is being lost at that point. mtr is distributed under the GNU General Public License version 2. See the COPYING file for details. (in the past, there was a Makefile in the distribution that did the ./configure for you and then ran make again with the generated Makefile, but this has suffered some bitrot. It didn't work well with git.) Note that mtr-packet must be suid-root because it requires access to raw IP sockets. See SECURITY for security information. On Solaris, you'll need to use GNU make to build. (Use gmake rather than make .) On Solaris (and possibly other systems) the "gtk" library may be installed in a directory where the dynamic linker refuses to look when a binary is setuid. Roman Shterenzon reports that adding -Wl,-rpath=/usr/lib to the commandline will work if you are using gnu LD. He tells me that you're out of luck when you use the sun LD. That's not quite true, as you can move the gtk libraries to /usr/lib instead of leaving them in /usr/local/lib . (when the ld tells you that /usr/local/lib is untrusted and /usr/lib is trusted, and you trust the gtk libs enough to want them in a setuid program, then there is something to say for moving them to the "trusted" directory.) Using mtr on Windows requires Windows Subsystem for Linux (WSL). To install WSL with Ubuntu distribution (Default), see How to install Linux on Windows with WSL. Next, re-run cygwin's setup-x86.exe (or setup-x86 64.exe if you're using 64bit cygwin) with the following arguments, Bug reports and feature requests should be submitted to the Github bug tracking system. Patches can be submitted by cloning the Github repository and issuing a pull request, or by email to me. Please use unified diffs. Usually the diff is sort of messy, so please check that the diff is clean and doesn't contain too much of your local stuff (for example, I don't want/need the "configure" script that /your/ automake made for you). (There used to be a mailinglist, but all it got was spam. So when the server was upgraded, the mailing list died.)