MikroTik Diagnostic Tools — Ping, Traceroute & More
Summary MKController adds a Tools panel to any adopted MikroTik router so you can run live network diagnostics straight from the browser — Ping, Traceroute, DNS Lookup, Cable Test and Torch (live traffic) — without opening Winbox or typing a single command. Everything runs on the router itself through the MKController device tunnel, so it works even on routers behind CGNAT with no public IP. You read the results right there: reply times, hop-by-hop paths, resolved addresses, copper-pair status and top talkers.
What Are the MikroTik Diagnostic Tools in MKController?
Section titled “What Are the MikroTik Diagnostic Tools in MKController?”Every MikroTik router already ships with powerful command-line diagnostics — ping, traceroute, torch, cable-test and DNS resolution. The catch is that reaching them normally means opening Winbox or an SSH session to the device, remembering the exact command syntax, and reading raw terminal output. On a remote router behind CGNAT you first have to get a connection to the box at all.
MKController’s Tools panel puts those same diagnostics behind a button. You open the router in MKController, pick a tool, fill in a field or two (an address, a host, an interface), and the platform runs the command on the router and shows the parsed result — a latency summary, a hop table, resolved addresses, cable pairs, or a live traffic breakdown.
When Should You Use These Tools?
Section titled “When Should You Use These Tools?”| You need to… | Use |
|---|---|
| Check if the router can reach a host and how fast | Ping |
| See the path and where latency builds up to a destination | Traceroute |
| Confirm the router resolves a domain (and via which server) | DNS Lookup |
| Find a bad or broken Ethernet cable on a port | Cable Test |
| See what is using bandwidth on a link right now | Torch |
These answer the everyday field questions — “is the link actually up?”, “where does the path break?”, “why is this interface saturated?”, “is this a cable fault or a config problem?” — without a truck roll and without handing a technician Winbox credentials.
How Do the Tools Work?
Section titled “How Do the Tools Work?”When you run a tool, MKController sends the matching RouterOS command to the device through its secure tunnel and reads the result back. There is nothing to install on the router and no script to maintain — the tools use the same managed command channel that powers remote access, so they work the same whether or not the device has a public IP.
The tools fall into two groups:
- Instant tools — Ping, Traceroute, DNS Lookup, Cable Test. These finish in a few seconds and return a single result you read on the spot.
- Running tool — Torch. Torch runs longer, so MKController runs it as a background job with a progress bar and live partial results — its top-talkers table updates every couple of seconds while it samples. You can stop a running job at any time, and only one long job runs on a given router at a time so two of them never compete for the link.
Step-by-Step: Run a Diagnostic
Section titled “Step-by-Step: Run a Diagnostic”-
Log in to app.mkcontroller.com.
-
Open the Devices menu, find your MikroTik, and click View More.
-
Open the Actions menu (top right) and choose Tools. (The device must be online.)
-
Pick a tool, fill in the field it asks for — an address for Ping/Traceroute, a host for DNS, an interface for Cable Test and Torch — and click Run (or Start for Torch).
-
Read the result in the panel. For Torch, watch the progress bar fill; use Stop to end a run early.
A Note on Torch and Privacy
Section titled “A Note on Torch and Privacy”Torch shows what is consuming bandwidth on an interface. In MKController it is aggregated by protocol and port — for example tcp:443 or udp:53 — with a count of how many distinct hosts were seen, and it does not display individual client IP addresses. You get the signal you need to find what is saturating a link without turning a diagnostic into a surveillance tool.
Requirements and Limits
Section titled “Requirements and Limits”- The device must be online and adopted in MKController — the Tools item only appears when the router is reachable.
- Cable Test depends on the port’s PHY, so it is meaningful on Ethernet ports. If a model or version doesn’t support a command, the tool returns an empty result rather than failing hard.
- Running a tool requires the same device remote-access permission as the rest of the command features, so access follows your existing per-site user permissions.
Best Practices
Section titled “Best Practices”- Start with Ping, then Traceroute. Confirm reachability first; if it fails or is slow, trace the path to see where it breaks.
- Use Torch on the WAN interface to find the top talkers when a link is saturated, and on a LAN/bridge interface to see internal traffic.
- Run Cable Test on a suspect port before sending a technician — a failed pair points straight at a physical fault.
Frequently Asked Questions
Section titled “Frequently Asked Questions”Do I need Winbox or SSH to use these tools? No. MKController runs the diagnostics on the router through its managed tunnel and shows you the parsed results in the browser. You don’t open Winbox, start an SSH session, or type any command.
Do the tools work on a router behind CGNAT with no public IP? Yes. They use the same device tunnel as the rest of MKController, so they run and report the same way whether or not the device has a public IP.
Does Torch show my clients’ IP addresses? No. Torch is aggregated by protocol and port and reports only a count of distinct hosts — individual client IPs are not shown.
Why can’t I start a second Torch on the same router? Only one long-running job runs per router at a time so two of them never compete for the link. Wait for the current one to finish or stop it, then start the next.
Why does the Tools item not appear in the Actions menu? The device must be online for live diagnostics to run, so the item is hidden while the router is offline. It is also behind a feature rollout — if you don’t see it yet, contact support.
Cable Test returned nothing — is it broken? Not necessarily. Cable Test depends on the port hardware, so it is meaningful on Ethernet ports. When a command isn’t supported on that model or version, the tool returns an empty result instead of an error.
To monitor each link’s usage over time, see Monitor MikroTik Internet Link Usage. To keep a site online across ISP outages, see MikroTik WAN Failover.
Questions about the diagnostic tools for your fleet? Contact MKController support on WhatsApp.