DESCRIPTION
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 HOSTNAME by sending packets with
purposely low TTLs. It continues to send packets with low TTL,
noting the response time of the intervening routers. This
allows mtr to print the response percentage and response times of
the internet route to HOSTNAME. A sudden increase in packet
loss or response time is often an indication of a bad (or
simply overloaded) link.
The results are usually reported as round-trip-response times
in milliseconds and the percentage of packetloss.
I think Windows® has a similar function: mytraceroute.
I like to use the arguments:
-w ; Wide report
-c 9 ; Use 9 iterations in the report
-m # ; trace to a depth of #
Examples:
gelmce@nc8q-desktop:~/Pictures$ mtr
-w -c 9 nc8q-mvhs-kettering
Start: 2024-05-31T08:06:21-0400
HOST: nc8q-desktop Loss% Snt Last
Avg Best Wrst StDev
1.|-- localnode.local.mesh 0.0% 9
0.6 0.6 0.6 0.8 0.1
2.|-- dtdlink.NC8Q-Kettering-MVHS.local.mesh 0.0% 9
1.0 1.1 1.0 1.2 0.1
3.|-- NC8Q-MVHS-Kettering.local.mesh 0.0% 9
5.7 3.8 2.2 5.7 0.9
gelmce@nc8q-desktop:~/Pictures$
gelmce@nc8q-desktop:~/Pictures$ mtr -w -c 9 -m 9 w8lrj-bbush-mvhs
Start: 2024-05-31T08:09:47-0400
HOST: nc8q-desktop Loss% Snt
Last Avg Best Wrst StDev
1.|-- localnode.local.mesh 0.0% 9
0.6 0.6 0.5 0.7 0.0
2.|-- dtdlink.NC8Q-Kettering-MVHS.local.mesh 0.0% 9
1.0 1.0 1.0 1.1 0.1
3.|-- NC8Q-MVHS-Kettering.local.mesh 0.0% 9
6.6 3.7 2.8 6.6 1.2
4.|-- dtdlink.W8LRJ-MVHS-Beavercreek.local.mesh 0.0% 9
4.3 4.5 3.3 7.5 1.2
5.|-- W8LRJ-BBush-MVHS.local.mesh 0.0% 9
6.4 9.1 6.4 14.8 2.7
gelmce@nc8q-desktop:~/Pictures$