1MTR(8) mtr MTR(8)
2
3
4
6 mtr - a network diagnostic tool
7
8
9
11 mtr [-hvrctglspniu46] [--help] [--version] [--report] [--report-wide]
12 [--report-cycles COUNT] [--curses] [--split] [--raw] [--no-dns] [--gtk]
13 [--address IP.ADD.RE.SS] [--interval SECONDS] [--psize BYTES | -s
14 BYTES] HOSTNAME [PACKETSIZE]
15
16
17
19 mtr combines the functionality of the traceroute and ping programs in a
20 single network diagnostic tool.
21
22
23 As mtr starts, it investigates the network connection between the host
24 mtr runs on and HOSTNAME. by sending packets with purposly low TTLs.
25 It continues to send packets with low TTL, noting the response time of
26 the intervening routers. This allows mtr to print the response per‐
27 centage and response times of the internet route to HOSTNAME. A sudden
28 increase in packetloss or response time is often an indication of a bad
29 (or simply overloaded) link.
30
31
33 -h
34
35 --help
36 Print the summary of command line argument options.
37
38
39 -v
40
41 --version
42 Print the installed version of mtr.
43
44
45 -r
46
47 --report
48 This option puts mtr into report mode. When in this mode, mtr
49 will run for the number of cycles specified by the -c option,
50 and then print statistics and exit.
51
52 This mode is useful for generating statistics about network
53 quality. Note that each running instance of mtr generates a
54 significant amount of network traffic. Using mtr to measure the
55 quality of your network may result in decreased network perfor‐
56 mance.
57
58
59 -w
60
61 --report-wide
62 This option puts mtr into wide report mode. When in this mode,
63 mtr will not cut hostnames in the report.
64
65
66 -c COUNT
67
68 --report-cycles COUNT
69 Use this option to set the number of pings sent to determine
70 both the machines on the network and the reliability of those
71 machines. Each cycle lasts one second.
72
73
74 -s BYTES
75
76 --psize BYTES
77
78 PACKETSIZE
79 These options or a trailing PACKETSIZE on the commandline sets
80 the packet size used for probing. It is in bytes inclusive IP
81 and ICMP headers
82
83 If set to a negative number, every iteration will use a differ‐
84 ent, random packetsize upto that number.
85
86 -t
87
88 --curses
89 Use this option to force mtr to use the curses based terminal
90 interface (if available).
91
92
93 -n
94
95 --no-dns
96 Use this option to force mtr to display numeric IP numbers and
97 not try to resolve the host names.
98
99
100 -o fields order
101
102 --order fields order
103 Use this option to specify the fields and their order when load‐
104 ing mtr.
105 Example: -o "LSD NBAW"
106
107
108 -g
109
110 --gtk
111 Use this option to force mtr to use the GTK+ based X11 window
112 interface (if available). GTK+ must have been available on the
113 system when mtr was built for this to work. See the GTK+ web
114 page at http://www.gimp.org/gtk/ for more information about
115 GTK+.
116
117
118 -p
119
120 --split
121 Use this option to set mtr to spit out a format that is suitable
122 for a split-user interface.
123
124
125 -l
126
127 --raw
128 Use this option to tell mtr to use the raw output format. This
129 format is better suited for archival of the measurement results.
130 It could be parsed to be presented into any of the other display
131 methods.
132
133
134 -a IP.ADD.RE.SS
135
136 --address IP.ADD.RE.SS
137 Use this option to bind outgoing packets' socket to specific
138 interface, so that any packet will be sent through this inter‐
139 face. NOTE that this option doesn't apply to DNS requests (which
140 could be and could not be what you want).
141
142
143 -i SECONDS
144
145 --interval SECONDS
146 Use this option to specify the positive number of seconds
147 between ICMP ECHO requests. The default value for this parame‐
148 ter is one second.
149
150
151 -u
152 Use UDP datagrams instead of ICMP ECHO.
153
154
155 -4
156 Use IPv4 only.
157
158
159 -6
160 Use IPv6 only.
161
162
164 Some modern routers give a lower priority to ICMP ECHO packets than to
165 other network traffic. Consequently, the reliability of these routers
166 reported by mtr will be significantly lower than the actual reliability
167 of these routers.
168
169
170
172 For the latest version, see the mtr web page at http://www.bitwiz‐
173 ard.nl/mtr/.
174
175
176 Subscribe to the mtr mailing list. All mtr related announcements are
177 posted to the mtr mailing list. To subscribe, send email to major‐
178 domo@lists.xmission.com with subscribe mtr in the body of the message.
179 To send a message to the mailing list, mail to mtr@lists.xmission.com.
180
181
182 Bug reports and feature requests should be sent to the mtr mailing
183 list.
184
185
186
188 traceroute(8), ping(8).
189
190
191
192mtr March 4, 1999 MTR(8)