Feature Request: MTR

The only thing missing in the tools.

One of the best debugging tool ever
http://en.wikipedia.org/wiki/MTR_(software)

Yes, that would be helpful

+1, MTR is very userful tool

+1

good idea

There is already Traceroute.

yes yes, there is also already ping…

But for you here it is in more detail link .

If you r lazy, here is a summary:

The real advantage of mtr over ping or traceroute is, it shows where exactly the packet loss is happening in the route to the destination host in realtime. It shows the loss percentage on each hosts, which can give us valuable information on which specific provider is having a network issue. Also, since mtr is using ICMP ECHO requests, it will go through the routers which have blocked udp packets. So mtr may work where traceroute is not working.

So yes, mtr is a tool/feature which is good and needed, and no, there is no good excuse to exclude it.


rgrds

I will be very nice.

+1 Really helpful for track routing problems!.

So, it is like “pathping”.
For sure it is useful, I perform this this test opening a lot of ping’s windows…

MT team ?
I am sure a lot more people will find it useful too.

Also if possible, add it to v5.x :slight_smile:

+1 helpful

+1

Regards,

+1 Thanks

i would be great !!!
it is a basic linux troubleshooting tools , it should be in Mikrotik for ipv6 and v4, in live format with refresh interval input , reserve DNS option,packet loss in color ,

+1 yup

why can’t you use it from your PC? =)

Because my PC and I, are not in the same country with the network having difficulties.

Because when my PC and I are on the network having difficulties, return traffic may take a different path than traffic from my location out.

You don’t always know what is going on until you’ve looked at it from both ends.

these things are easily solved by tunneling to the router, it’s also more secure to manage your router if you are on an encrypted tunnel.

So, looks like no mtr, come on don’t be lazy. By the rate new versions are coming out u can put it in, doesnt actually have to work, it will be properly debuged in a year or so and usable a year after that. win-win

Copy/paste the source code, color output match with ROS console, make the basic frame in winbox, with one input, eventually 3-4 most used options.

How big is mtr compiled anyway ? :sunglasses:
All in all, ~35kb max !!

Its not that We/I are asking UDP in OVPN or rewrite of syslog format or whatever else regarding complex services in the ROS.
The necessity to need to make this tread so long, its depressing.