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.
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.
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
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:
Depending on the network setup, you may not get the hostname.
There are 2 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
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
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
The search utility is a fairly handy tool:
http://www.commandlinefu.com/commands/view/619/ping-a-range-of-ip-addresses
@ 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.