What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags





mtr, better than traceroute and ping combined

Terminal - mtr, better than traceroute and ping combined
mtr google.com
2009-02-21 07:53:32
User: fryfrog
mtr, better than traceroute and ping combined

mtr combines the functionality of the traceroute and ping programs in a single network diagnostic tool.

As mtr starts, it investigates the network connection between the host mtr runs on and HOSTNAME. by sending packets with purposly low TTLs. It continues to send packets with low TTL, noting the response time of the intervening routers. This allows mtr to print the response percentage and response times of the internet route to HOSTNAME. A sudden increase in packetloss or response time is often an indication of a bad (or simply over‐loaded) link.


There is 1 alternative - vote for the best!

Terminal - Alternatives
mtr google.com
2012-02-19 22:27:48
User: d_voge

You need to have mtr installed on your host.

Know a better way?

If you can do better, submit your command here.

What others think


Your command line works great. i get some interesting information

from the traceroute and it keeps the information updated. im running

ubuntu EEE (easy Peasy) 8.10 on my netbook.

Greets Snipercup

Comment by snipercup 352 weeks and 5 days ago

Droool.. this is awesome, im hypnotized!

Comment by foucault 352 weeks and 5 days ago

Great command! Thanx for sharing.

Comment by betsubetsu 352 weeks and 5 days ago

Great one.. Thanks..

Comment by ergut 352 weeks and 4 days ago

To run in terminal do:

mtr -t

Great tool! Thanks!

Comment by nongeekboy 350 weeks and 3 days ago

I like to use

mtr -r -c 100

You don't get to watch but it'll print the statistics. You win some, you lose some.

Comment by brie 301 weeks and 6 days ago

The homebrew system is a great way to get this tool on OSX, btw -> http://github.com/mxcl/homebrew

Comment by 4fthawaiian 300 weeks and 6 days ago

great one, thanks for sharing!

Comment by KoRoVaMiLK 296 weeks and 2 days ago

Love this! Also love brie's example however I find 100 take's quite a while to report.

Thanks to the both of you this is super handy!

Comment by danstinebaugh 274 weeks and 3 days ago

great, thanks!

Comment by maneeshshetty 248 weeks and 6 days ago

Hi this a good command but this have a problem, is detected by the firewall , with many connections to dns provider probably your machine will be block by firewall,

Comment by aarntesla 246 weeks and 5 days ago

tl;dr: mtr provides false reports.

It's worth mentioning a few things. First, ICMP packets must be processed by the control plane of a router or switch. "Normal" packets, however, are switched by hardware ASICs (in provider cores and some business devices).

This means that you could see "latency" and/or "packet loss" where there is none. In addition to being processed by the control plane, ICMP is often either rate-limited, blocked, policed, or otherwise handled differently than "normal" traffic.

What I'm trying to point out is that it's important to not just understand WHAT your tool does, but HOW it does it and how the results may be affected. This is true for any tool, but in my work I've seen many rely on results of "ping plotter" and "mtr" and similar tools to determine trouble and it is simply not always accurate. Service provider devices (particularly devices manufactured by Cisco) tend to have very weak processors. Poor network design (with regards to control plane tasks such as BGP scanning and SPF calculations) can also lead to false reports of packet loss.

Comment by pkttlk 151 weeks and 2 days ago

To install this using Macports, do

sudo port install mtr
Comment by cma 150 weeks and 1 day ago

Your point of view

You must be signed in to comment.