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.

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.

OpenID
or
Sign in Register

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

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

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

List alive hosts in specific subnet

Terminal - List alive hosts in specific subnet
nmap -sP 192.168.1.0/24
2010-06-05 14:48:37
User: sdadh01
20
Up
Down
List alive hosts in specific subnet

Works on any machine with nmap installed. Previous version does not work on machines without "seq".

Also works on subnets of any size.

Show sample output | Add to favourites | Report as malicious

Alternatives

There are 6 alternatives - vote for the best!

Terminal - Alternatives
for ip in `seq 1 255`; do ping -c 1 192.168.1.$ip ; done | grep ttl
2010-06-05 13:15:06
User: takeshin
Functions: grep ping
Tags: Network ping loop ip address hosts
0
Up
Down
List alive hosts in specific subnet
Comments (1) | Add to favourites | Report as malicious
for i in 192.168.1.{1..254} ; do if ping -c1 -w1 $i &>/dev/null; then echo $i alive; fi; done
2010-06-12 18:38:36
User: wiburg
Functions: echo ping
Tags: Network ping loop ip address hosts
-2
Up
Down
List alive hosts in specific subnet
Comments (0) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

The nmap command above will work, but can go a lot faster if you don't have to do DNS lookups for each of the IP's.

Ex.:

nmap -sP -n 192.168.1.0/24

On my network, the original command takes 14.176 seconds, while the second takes 3.812.

Comment by jaymcjay 150 weeks and 5 days ago

you won't find nmap on every Linux system. Forget it when you're on an older UNIX system. Yall' shouldn't diss the 'for loop' version just for being 'too long'. It sometimes come in handy.

Comment by unefunge 130 weeks and 4 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts