Hide

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.

Get involved!

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

OpenID
or
Sign in Register

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.
Hide

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:

Hide

News

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!
Hide

Top Tags


awk, bash, curl, find, grep, Linux, sed
Hide

Functions

Hide

Credits

Maintained by Jon H.

Site originally by David Winterbottom (user root).

Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Show all machines on the network

Terminal - Show all machines on the network
nmap 192.168.0-1.0-255 -sP
2009-03-23 22:19:05
User: clockworkavian
4
Up
Down
Show all machines on the network

Depending on the network setup, you may not get the hostname.

Show sample output | Add to favourites | Report as malicious

Alternatives

There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

it takes CIDR notation as well

nmap -sP 192.168.0.2/24

you can also use

nmap -vv -sP 192.168.0.2/24 |grep up

that way you skip all the hosts that are down

Comment by chinkshady 430 weeks and 3 days ago

The -sP option is basically sending ICMP echo requests.

Some hosts may be configured to not respond to these.

Alternative is to ping the broadcast address.

eg: ping -c 4 192.168.0.255

and display the arp table: arp -a

Comment by mpb 430 weeks and 3 days ago

The search utility is a fairly handy tool:

http://www.commandlinefu.com/commands/view/619/ping-a-range-of-ip-addresses

Comment by atoponce 430 weeks and 2 days ago

@ chinkshady:

I used to use the CIDR for it, but I wanted a really quick list, and over both the 192.168.0.* and 192.168.1.* ranges. I could use CIDR /16, but that takes considerably more time, and scans a lot of uncommon network configurations. I used to grep for my IP, but it's really uneccessary.

@mpb:

That is neat! I've been looking for a way to get around that limitation. Sadly, the arp lookup is really slow, and only returns two of 8 hosts currently running on my network.

@ atopnce:

Yeah, I realized that immediately afterward :-/. I will do better next time. However, I did use more newbie friendly search terms, with the net effect, rather than the literal description of the process, so I decided to keep it up.

Comment by clockworkavian 430 weeks and 1 day ago

Your point of view

You must be signed in to comment.