Skip to main content
Back to Category

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.

Read time: 8 min Troubleshooting
mtrwinmtrnetwork testpingicmptroubleshootingtraceroutepacket loss
Author
REXE Teknoloji Network & Security Team
Editor
REXE Teknoloji Technical Editorial
First published
Last updated

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

  1. Log in to Path Panel (my.rexe.tr → Path Panel)
  2. Go to IP Management → Click your server IP
  3. 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

  1. Download WinMTR from sourceforge.net/projects/winmtr
  2. Enter your server IP in the Host field
  3. Click Start
  4. Wait for at least 150 passes
  5. Click Export TEXT to save results

Linux — MTR Command

hljs bash
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

  1. Save both MTR results
  2. Create a support ticket at my.rexe.tr
  3. Attach the MTR result files
  4. Include: when the issue started, which service is affected, whether it's constant or intermittent

Reading MTR Results

ColumnDescription
HostNetwork hop IP address
Loss%Packet loss percentage
SentPackets sent
RecvPackets received
BestLowest latency (ms)
AvrgAverage latency (ms)
WrstHighest 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).

Frequently Asked Questions

Why isn't my MTR test working?

ICMP is blocked by default in the Path.net firewall. Enable the Ping toggle in the Path Panel and wait 2-5 minutes.

How many packets should I send?

Send at least 150 packets (passes) for reliable statistics.

I see high packet loss in MTR results — is this a serious problem?

Packet loss at intermediate hops is usually not a problem; some routers deprioritize ICMP. What matters is the packet loss at the final hop (destination server). If the last hop shows 5% or more packet loss, contact the support team.

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.

8 min
sshconnection problemtroubleshooting
Network TrafficInbound— GbpsOutbound— Gbps