🛰️ How to Run an MTR

To diagnose network issues, you need to run an MTR in both directions:

• From the server to the client.
• From the client to the server.

Each test should be run with a minimum of 200 packets.

The results must be saved in two text files (.txt), one for each test direction.
Each file name should include the source and destination IPs for better identification.

If you only have hosting, you only need to send the MTR towards the server.

Example file names:

• Client_192.168.1.1_to_Server_45.149.101.1.txt
• Server_45.149.101.1_to_Client_192.168.1.1.txt

🧰 What is MTR?

MTR (My Traceroute) is a network diagnostic tool that combines the functionalities of traceroute and ping. It analyzes the route packets take from a source to a destination, showing detailed statistics on latency and packet loss at each intermediate hop.

This is especially useful for identifying and locating connectivity issues in the network.

🛡️ Configure the Firewall for ICMP

Before running MTR tests, make sure ICMP traffic is allowed in the firewall. Generally, we already have a rule created to allow ICMP:

Option	Value	Notes
Rule Name	ICMP Whitelist – Global	You can name it as you prefer
Source IP	0.0.0.0/0	Allows ICMP from any IP
Protocol	ICMP
Source Port	Empty	ICMP does not use ports
Destination Port	Empty
Action	Allow	Enables ICMP communication

⚠️ Wait up to 10 minutes after creating this rule for it to propagate through the network.
If it still doesn't work after that time, check if the operating system is blocking ICMP locally.

🖥️ Run MTR from Windows

1. Download WinMTR from:
   https://sourceforge.net/projects/winmtr/files/WinMTR-v092.zip/download

2. Extract the ZIP file and run WinMTR.exe from the appropriate folder (usually 64-bit).

3. In the Host field, enter the server or client IP (for example: 45.149.101.1).

4. Click Start to begin the test.

5. Let it run until the "Sent" and "Recv" fields exceed 200 packets.

6. Click Export TEXT.

7. Save the file as:
   Client_192.168.1.1_to_Server_45.149.101.1.txt or Server_45.149.101.1_to_Client_192.168.1.1.txt

📡 Run MTR from Linux

1. Install mtr if you don't have it yet:

   sudo apt install mtr

2. Run the following command from the server to the client or server IP:

   mtr -c 200 IP

   example: mtr -c 200 45.149.101.1

   • -c 200: Number of packets, wait until it finishes.

     

3. Save the result in a text file, for example:
   Client_192.168.1.1_to_Server_45.149.101.1.txt or Server_45.149.101.1_to_Client_192.168.1.1.txt

4. Attach the TXT results to the support ticket.

📤 Sending Results

• Make sure to run tests in both directions.
• Save each result in a .txt file.
• Use descriptive file names with source and destination IPs.
• Attach the files to the ticket or send them to the appropriate support team.
• If you can't name them correctly, indicate the public IP in the message and in the .txt file.

---

Running accurate MTR tests in both directions can be crucial for detecting real connectivity issues. It provides valuable data to the support team to resolve your issue faster