

#MTR REPORT MANUAL#
To get more details on the available mtr options you can read either the manual with man mtr or press ‘h’ during the interactive console. Of course, part of the packet loss can be ICMP rate limiting as well. That tells us that the packet loss is real, and the subsequent hops are impacted by the packet loss on hop 11 as well as whatever other new losses come into play. On hop 3, we see a 3.7% packet loss, which tells us that the 27.9% packet loss we see on hop 2 is most likely due to ICMP rate limiting by the router and not actual packet loss.Ĭompare that with the columns 11-20: we see that the packet loss after hop 11 is at least as high as 21.3%. In the above example, on the second hop we see a packet loss of 27.9% on my home router (192.168.1.254 ), which would raise an alert. Mtr has the limitations of the traceroute: if a route has rate limiting or completely rejects ICMP traffic, then mtr (and traceroute) will display a high packet loss, but in reality normal data traffic might not experience any loss. 220.181.38.148 20.1% 134 183.8 176.3 170.9 201.9 3.9ġst column: The IP or name of each hop 2nd column: Percentage of packet lost per hope 3rd column: Number of packets sent 4th column: Latency as measured on the last packet sent 5-8th column: Average, best, worst and standard deviation of the latency for each hop Keys: Help Display mode Restart statistics Order of fields quitġ. If you type mtr, mtr launches an interactive console and runs continuously until you decide to stop it by pressing ‘q’. There are two main types of information it provides: packet loss and latency per hop. In most systems, that won’t be a problem, but it’s something to keep in mind. If your host doesn’t already have the libraries that mtr depends on, you may need up to 60MB of disk space for the installation.
#MTR REPORT INSTALL#
To install it on Debian based Linux hosts you just have to type: apt-get install mtr Mtr takes that to the next level by giving you the ability to run the probe packets continuously and produce statistics and baselines automatically over the number of probing packets. They both work the same way: a host sends probing packets to routers, measures and reports latency and packet loss. Mtr stands for “My Traceroute” and, in a nutshell, it’s traceroute on steroids.
