How to Run an MTR Test and Submit Results to Support
Guide to running MTR network tests with WinMTR and Linux MTR, creating ICMP filter rules, and submitting results to support. Diagnose packet loss and latency.
Table of Contents
Introduction
MTR (My Traceroute) is an advanced network diagnostic tool that combines ping and traceroute. It's used to identify packet loss and latency points in the network path.
MTR uses the ICMP protocol. ICMP is blocked by default in the Path.net firewall. You must create an ICMP filter rule before testing.
Step 1: Create ICMP Filter Rule
- Log in to Path Panel (my.rexe.tr → Path Panel)
- Go to IP Management → Click your server IP
- Set the "Ping On/Off" toggle to On
When the Ping toggle is enabled, the ICMP filter rule is created automatically. The rule may take 2-5 minutes to propagate. Since the ICMP rule also counts as a rule, enabling Ping while your IP has no other rules automatically triggers Default Block and disallowed ports are closed.
Step 2: Run MTR Test
Windows — WinMTR
- Download WinMTR from sourceforge.net/projects/winmtr
- Enter your server IP in the Host field
- Click Start
- Wait for at least 150 passes
- Click Export TEXT to save results
Linux — MTR Command
sudo apt install mtr -y
mtr -r -c 150 SERVER_IP_ADDRESS > mtr_result.txt
Step 3: Bidirectional Test
Run MTR in both directions:
- From your computer → Server
- From server → Your computer
Bidirectional testing is crucial. Single-direction tests may not identify which direction has the issue.
Step 4: Submit Results
- Save both MTR results
- Create a support ticket at my.rexe.tr
- Attach the MTR result files
- Include: when the issue started, which service is affected, whether it's constant or intermittent
Reading MTR Results
| Column | Description |
|---|---|
| Host | Network hop IP address |
| Loss% | Packet loss percentage |
| Sent | Packets sent |
| Recv | Packets received |
| Best | Lowest latency (ms) |
| Avrg | Average latency (ms) |
| Wrst | Highest latency (ms) |
Packet loss at intermediate hops doesn't always indicate a problem. Some routers deprioritize ICMP. What matters is the loss at the final hop (server).
Related Articles
SSH Connection Problem: Can't Connect to Server
SSH connection troubleshooting guide: Path.net firewall rules, Default Block, creating a filter rule for SSH port, and step-by-step troubleshooting.
RDP Connection Problem: Can't Connect to Windows Server
RDP connection troubleshooting guide: Path.net firewall rules, Default Block, creating a filter rule for RDP port, and step-by-step troubleshooting.
How to Capture Packets (PCAP) and Submit to Support
Packet capture guide using Linux tcpdump and Windows Wireshark. Create PCAP files for network analysis, troubleshoot connectivity issues, and submit to support.