The MTR (My traceroute) is a network diagnostic tool that incorporates pings and traceroute into a single program. The MTR provides two interfaces: a ncurses interface that is useful for using MTR from a Telnet session, and a GTK + interface for X (provided in the MTR-GTK package).
MTR use
1. MTR Command line tools
MTR is easy to use, please refer to the man page of MTR for detailed usage.
[Email protected] ~]# Mtr–help
usage:mtr [-hvrctglspni46] [help] [–version] [–report]
[–report-cycles=count] [–curses] [–GTK]
[–raw] [–split] [–no-dns] [–address Interface]
[–psize=bytes/-s bytes]
[–interval=seconds] HOSTNAME [PacketSize]
The main parameters are explained as follows:
–report trace results in report mode output
–report-cycles=count defines the number of traces, the default is 16
–raw to output the result in the original format
–split the results of each trace separately, not like –report, to count the entire result
–no-dns only displays IP addresses, does not resolve host names corresponding to IP addresses
–psize=bytes/-s bytes defines the size of the packet, in bytes
Mtr-h provide help commands
Mtr-v displaying the version information of the MTR
Mtr-r reported mode display
Mtr-s used to specify the size of the ping packet
Mtr-nno-dns IP address does not do domain name resolution
Mtr-a to set the IP address of the sending packet this is useful for a host by multiple IP addresses
Mtr-i Use this parameter to set the requirement between ICMP returns by default is 1 seconds
Mtr-4ipv4
Mtr-6ipv6
Like what:
[Email protected] ~]# mtr--report-c 10-n nc.sias.edu.cn
Host:ly2 loss% Snt last AVG best Wrst StDev
1.10.10.10.3 0% 10 0.2 0.2 0.1 0.2 0.0
2.124.205.89.129 0% 10 0.4 33.7 0.3 89.1 43.1
3.192.168.182.133 0% 10 1.2 32.6 1.1 83.8 36.4
4.210.75.96.154 20% 10 0.9 42.3 0.9 87.7 36.6
5.10.255.27.205 0% 10 1.1 28.5 1.1 70.3 31.6
6.124.205.98.141 0% 10 3.0 25.7 1.0 86.9 33.7
7.124.205.98.57 0% 10 2.1 32.4 1.3 113.3 45.0
8.202.99.1.77 0% 10 1.3 32.4 1.2 106.5 45.1
9.10.15.253.229 0% 10 2.1 38.4 2.1 130.8 49.7
Ten.??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.113.57.231.1 0% 10 31.3 58.7 21.8 139.0 47.7
12.218.106.127.246 0% 10 25.4 66.7 21.1 158.6 57.7
13.58.19.112.17 40% 10 64.1 99.9 64.1 173.3 54.5
14.219.158.18.113 0% 10 71.7 103.0 69.2 176.0 41.8
15.219.158.96.22 0% 10 70.0 102.1 63.7 189.1 50.7
16.61.168.195.74 0% 10 67.1 99.9 64.0 209.7 52.8
17.125.42.110.18 10% 10 78.4 95.2 73.5 172.8 38.5
???. 100.0 10 0.0 0.0 0.0 0.0 0.0
As a result, you can visually see the minimum/maximum time and standard deviation of packet loss and ping commands from my host to the routed nodes that pass through and to each node.
Report Description:
First column: The IP address and the native domain name are displayed, which is like tracert
Second column: Snt:10 sets the number of packets sent per second, the default value is 10 can be specified by the parameter-C.
Where-C is the description:--report-cycles COUNT
Column Three: is the packet loss rate for each corresponding IP displayed
Fourth column: The most recent return delay shown
Fifth column: Is the average this should be the mean time delay for sending ping packets
The Sixth column: is the best or the shortest delay
The seventh column: The worst or the most frequent delay
Eighth column: is the standard deviation
linux-Common Commands-mtr