mtr reports does not work with high latency links

Solution Unverified - Updated -

Issue

  • The mtr on high latency connections there is often false positives for packet loss on the last few hops because the replies don't arrive before the timeout. It would be nice to have an option to specify a higher timeout when testing high latency connections to obtain an accurate report.

Environment

  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content