Report the established connections for a particular port

export PORT=11211; ss -an4 | grep -E "ESTAB.*$PORT" | awk '{print $5}' | awk -F: '{print $1}' | sort | uniq -c | sort -nr

2014-04-25 13:15:48

What Others Think

Hmm... first I tried to do this entirely in awk, but that got a bit complicated. Instead, I've gone for replacing your "grep;awk;awk" with one "sed": export PORT=11211; ss -an4 | sed -n '/ESTAB.*:'$PORT' .*:/{s/.* \([^:]\+\):.*:.*/\1/p}' | sort | uniq -c | sort -nr It consists of three parts. A search: '/ESTAB.*:'$PORT' .*:/ A replace: s/.* \([^:]\+\):.*:.*/\1/ and print sed -n ... p
flatcap · 397 weeks and 1 day ago
this provides a very different report. export PORT=11211; ss -an4 | grep -E "ESTAB.*$PORT" | awk '{print $5}' | awk -F: '{print $1}' | sort | uniq -c | sort -nr 34 33 33 32 31 30 29 28 27 26 4 export PORT=11211; ss -an4 | sed -n '/ESTAB.*:'$PORT' .*:/{s/.* \([^:]\+\):.*:.*/\1/p}' | sort | uniq -c | sort -nr 256
hornetmadness · 397 weeks and 1 day ago
This is interesting. I had not yet played with "ss". I thought I could cut out some of the pipes to make it all faster while still using ss, but I couldn't. I did find a slightly different approach. PORT=22 ; ss -n4 -o state established "( dport = :$PORT or sport = :$PORT )" | awk -F ':| +' '$1 ~ /[0-9]+/ {print $5}' | sort | uniq -c | sort -nr I also noticed that when I had PORT=22 the 'grep -E "ESTAB.*$PORT"' also matched port 8022. It should probably at least be changed to: grep -E "ESTAB.*:$PORT " I also tried with lsof, but that was much slower: PORT=ssh ; lsof -itcp:$PORT -stcp:established -n |awk -F '>|:| +' '$2 ~ /[0-9]+/ {print $11}' | sort | uniq -c | sort -rn
pdxdoughnut · 396 weeks and 5 days ago

What do you think?

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.

What's this? 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.

Share Your Commands

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.


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: