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/
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:
This command will display only the hosts that are active in the network.
There is 1 alternative - vote for the best!
Today many hosts are blocking traditional ICMP echo replay for an "security" reason, so nmap's fast ARP scan is more usable to view all live IPv4 devices around you. Must be root for ARP scanning.
If you can do better, submit your command here.
You must be signed in to comment.
The awk bit also catches the summary line at the end as it stands. If you just want the hosts, try this:
nmap -sP your network/submask | awk "/^Host/"'{ print $2 }'Mmmm, yes =)
Thanks
Command exists in here several times. Do try a grep of the archive before posting. In your defense, I got this same message for my first post. Ironically, for this same command :-/
Also, on networks that allow named hosts (like mine), the line reads
#Host aveil (192.168.0.144) appears to be up.and so you would print out the machine name, not the network. Machines that don't have names, will then cause both ips and names to print out, which would look odd.
lan|grep Host |grep -oE '[0-9]+\.[0-9\.]+'will filter out only IP addresses from such networks.