MTR results are sorted into rows and colums. Whilst MTR results are fairly self explanatory there are a number of important points that you should note when analysing the results which are detailed below: Reading MTR Results Set Packet Size – Using the -s flag you can specify the packet size (default 64 bytes).Force TCP or UDP – This can be achieved with –udp or –tcp.Change Interval – The default interval is 1 second, you can change this to a higher or lower value by using the -i flag.Save Results to a File – Adding the > “filename” at the end of your MTR command will save the results to a file with that name.IP and Hostnames – You can add the “-b” flag to display IPs and Hostnames.IPv4 Only – You can add the “ -4″ flag onto the end of your MTR command to force MTR to use IPv4 and not lookup RDNS records.To install MTR on RHEL, CentOS and Fedora operating systems you can run: yum install mtrĪn mtr can be invoked from a linux terminal simply by typing mtr followed by the URL or IP you want to run the test to for example: mtr MTR Options in Linux To install MTR on Debian and Ubuntu operating systems you can run: apt install mtr-tiny This is normally best left at a default of 1 second however can be highered (possibly for reducing the impact of ICMP rate limiting explained below) or lowered for a more sensetive test. Interval (sec) – This is the interval at which the ICMP traffic will be sent to the routers along the path to your host.Resolve names – Reverse DNS entries can be changed by an IP provider and make it difficult to see on which network your packet loss is appearing, sometimes therefore it is wise to just untick the box and manually lookup IPs using a WHOIS to find the network operator rather than resolving DNS.This is useful if you need to have Jumbo Frames enabled on your network and wish to test the MTU across a network. This is best left as default (64 bytes) for standard network troubleshooting however you can increase the bite size if required. There is a limited number of options available within WinMTR indicated below: Once installed the software will look like this, simply enter a website or IP address into the host box and click start to initiate your MTR. Please note as Windows uses “WinMTR” this provides a limited feature set and the full choice of options when running the test is only available within Linux or MacOS X. The latest release winmtr-0-92 can be downloaded here from the Fraction Servers website for both 32Bit and 64Bit operating systems, once downloaded simply extract the zip file and open the application. MTR runs on windows in a standalone application and is very simple to download and install on Windows. We recommend WinMTR for use on machines running Windows Operating Systems however as an alternative, Windows also has a program built in called pathping which works in a similar way and more details can be found on Microsoft’s website here. As MTR runs continuously it offers significant advantages over a traceroute because the output is updated continuously. What is MTRīy now you are probably familiar with basic network diagnostic tools such as ping and traceroute, MTR effectively combines these tools into one using ICMP packets to measure the availability of routers and the time take to travel between hops. MTR can be ran on Windows, MacOS or Linux. MTR originally stood for Matt’s Traceroute though is now more commonly known as “My traceroute” it is an invaluable tool for diagnosing network issues such as speed issues, high latency or packet loss.
0 Comments
Leave a Reply. |