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).

Read just the IP address of a device

Terminal - Read just the IP address of a device
/sbin/ifconfig | grep inet | cut -f 2 -d ":" | cut -f 1 -d " "
2009-07-21 21:42:04
User: random_bob
Functions: cut grep
-1
Up
Down
Read just the IP address of a device

another way to output the IP address' of the system

Add to favourites | Report as malicious

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
/sbin/ip -f inet addr | sed -rn 's/.*inet ([^ ]+).*(eth[[:digit:]]*(:[[:digit:]]+)?)/\2 \1/p' | column -t
2009-12-17 19:48:28
User: owen
Functions: column sed
1
Up
Down
Read just the IP address of a device
Comments (0) | Add to favourites | Report as malicious
ifconfig -l | xargs -n1 ipconfig getifaddr 2> /dev/null
2009-12-28 22:45:45
User: w216
Functions: ifconfig xargs
0
Up
Down
Read just the IP address of a device
Comments (0) | Add to favourites | Report as malicious
/sbin/ifconfig | awk -F'[ :]+' '/inet addr/{print $4}'
2009-07-21 14:18:17
User: inof
Functions: awk
-1
Up
Down
Read just the IP address of a device

That one works on Linux. On BSD and Solaris, the ifconfig output is much easier to parse:

/sbin/ifconfig -a | awk '/inet/{print $2}'
Comments (2) | Add to favourites | Report as malicious
/sbin/ifconfig | grep inet | cut -f 2 -d ":" | cut -f 1 -d " " |egrep -v "^$"
2009-07-22 07:27:54
User: giray
Functions: cut egrep grep
-1
Up
Down
Read just the IP address of a device

to clean up the extra lines

Show sample output | Comments (0) | Add to favourites | Report as malicious
ip addr|grep "inet "
2009-07-22 07:38:06
User: RickDeckardt
Functions: grep
-3
Up
Down
Read just the IP address of a device

Shows a single line per interface (device), with its IPv4 settings.

Shorter command, better readability in output.

Show sample output | Comments (4) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

the "IP address of a device" is a misconception. A device may have several interfaces with several address each. ?What is the "IP of the device" in this case? The better candidate is the inteface used to get the local gateway, but it may be several gateways too...

Comment by prayer 204 weeks ago

I've never worked with a multi-port NIC myself, but always assumed they'd have separate /dev entries for each port. is this not true?

Comment by random_bob 201 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts