Nmap scan report for thunderbolt.example.com (192.168.1.1) Host is up (0.0020s latency). Nmap scan report for vyatta.example.com (192.168.1.2) Host is up (0.0019s latency). Nmap scan report for sdadh01.example.com (192.168.1.51) Host is up (0.0075s latency). Nmap scan report for cua01.example.com (192.168.1.61) Host is up (0.0013s latency). Nmap done: 256 IP addresses (4 hosts up) scanned in 0.02 seconds
Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?
You must be signed in to comment.
commandlinefu.com is the place to record those command-line gems that you return to again and again. 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.
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:
nmap -sP -n 192.168.1.0/24
On my network, the original command takes 14.176 seconds, while the second takes 3.812.