XML version. Additionally it may give your geolocation if it's known by hostip.info Show Sample Output
List all the machine ip's currently running on your network Show Sample Output
you can use a pair of commands to test firewalls.
1st launch this command at destination machine
ncat -l [-u] [port] | cat
then use this command at source machine to test remote port
echo foo | ncat [-u] [ip address] [port]
First command will listen at specified port.
It will listen TCP. If you use -u option will listen UDP.
Second command will send "foo" through ncat and will reach defined IP and port.
Show Sample Output
Replace "en1" with your network interface (on OS X, usually en0, en1, eth0, etc..) Show Sample Output
If you need to ssh into a computer on the local network but you're unsure of the ip to use, then ping them and see if you get a response. If you do, print out the address you got it from. Adjust the range to suit your network.
Require ips and ipcalc Show Sample Output
With a lolcat favicon if you access it from your browser Show Sample Output
Here's a version that uses netcat (although I'd much rather use curl!).
Find your default gateway and print it directly output http://www.bilgisayarmatematik.com/ kerim@bayner.com Show Sample Output
Linux specific, requires iproute2 (but most distros have that by default now)
No junk, no pipe, one command, no subcommand - KISS Show Sample Output
ip.telize.com (Listen on both IPv4 and IPv6) ip4.telize.com (Listen on IPv4 only) ip6.telize.com (Listen on IPv6 only) More information on : http://www.telize.com
bash neto..
If curl isn't available, use lynx.
Another simple way to get external IP or use: wget -qO- http://ipecho.net/plain
On Linux and Mac systems (I have not tested with other Unix systems), the ping command will keep on pinging until the user interrupts it with Ctrl+C. On Windows system, ping will execute for a number of times then quit. The -c flag on Linux and Mac will make this happen
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: