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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.