Commands matching netstat (162)
-
This is also perl-less, and only uses AWK as its postprocessor. Tested with GAWK and MAWK.
0netstat -tan | awk '$1 == "tcp" && $4 ~ /:/ { port=$4; sub(/^[^:]+:/, "", port); used[int(port)] = 1; } END { for (p = 32768; p <= 61000; ++p) if (! (p in used)) { print p; exit(0); }; exit(1); }' -
Show state of NAT, readed from '/proc/net/ip_conntrack' or '/proc/net/nf_conntrack' Show Sample Output
0netstat-nat -n -
cut -f1,2 - IP range 16 cut -f1,2,3 - IP range 24 cut -f1,2,3,4 - IP range 24 Show Sample Output
0netstat -tn | grep :80 | awk '{print $5}'| grep -v ':80' | cut -f1 -d: |cut -f1,2,3 -d. | sort | uniq -c| sort -n -
Count on a specific port (80) - FreeBSD friendly. Show Sample Output
0netstat -an | grep 80 | wc -l -
0netstat -antu | awk '$5 ~ /[0-9]:/{split($5, a, ":"); ips[a[1]]++} END {for (ip in ips) print ips[ip], ip | "sort -k1 -nr"}'
-
0netstat -tuapen | grep LISTEN
-
I used this to get all the remote connection ip addresses connected to my server... I had to start storing and tracking this data so thats why i built this out... probably not optimal as far as the egrep regex but it works ;) Show Sample Output
0netstat -tn | awk '{print $5}' | egrep -v '(localhost|\*\:\*|Address|and|servers|fff|127\.0\.0)' | sed 's/:[0-99999999].*//g' -
This has saved me many times while debugging timeout issues to "too many open files" issues. A high number of the order of thousand, indicates that somewhere connection is not being closed properly. Show Sample Output
0while true; do netstat -a|grep WAIT|wc -l; sleep 5; done -
bit of a contrived example and playing to my OCD but nice for quick scripted output of listening ports which is sorted by port, ip address and protocol. Show Sample Output
0sudo netstat -plntu --inet | sort -t: -k2,2n | sort --stable -t. -k 1,1n -k 2,2n -k 3,3n -k 4,4n | sort -s -t" " -k1,1 -
Should work with sh, bash, etc. Show Sample Output
0port=32768; while netstat -atn | grep -q :$port; do port=$(expr $port + 1); done; echo $port -
Doesn't list connections to other ports than port 80. Not f.e. 8080 or 8091. Excludes programs listening for connections, like your favorite webserver.
0watch "netstat -plan | grep -v LISTEN | grep \":80 \" | awk {'print \$5'} | cut -d: -f 1 | uniq -c | sort -nk 1" -
netstat will list all open ports on the system, unix sockets, tcp sockets and udp sockets. the t flag limits to tcp ports the l flag limits to listening ports and the n flag disables the translation of port to service ( ie :25 displayed instead of :smtp ). then grep for the port you are interested in preceeded by a colon. Show Sample Output
0netstat -tln | grep :25 -
0netstat -np --inet|awk '/firefox/{split($5,a,":");z[a[1]]++} END{for(i in z){system("whois " i)}}'|less
-
-t TCP -u UDP -n NO DNS resolution or PORT/SERVICE resolution -l state -a ? -p PORT show -o flag (keepalive, off, etc)
0netstat -tunlapo -
Show If Someone Is Connected To The Android Device On And Get Their IP Address
0netstat -lptu | grep -E "22.*ESTABLISHED" | cut -s -d ':' -f2 | awk '{print $2}' -
0netstat -anp | grep ":<port>"
-
0netstat -nr|egrep -v "Routing|Interface|lo0"|awk '{print $5}'|sort -u| while read l; do ifconfig $l ; echo " Station Addr: `lanscan -ia|grep "$l "|cut -d ' ' -f 1`" ; done
-
0sudo netstat -tulpn | grep :8080
-
0netstat -anop tcp | find ":8010"
-
0netstat -tapn|grep LISTEN
-
Useful to see what ports are taken by running services. Show Sample Output
0netstat -ltn | awk -n '/tcp /{ split($4, x, ":"); print(x[2]); }' | sort -n -
This can be added to ~/.bashrc with your other shell aliases. Emulates similar look & feel to ping6 & traceroute6. Show Sample Output
0alias netstat6='netstat --inet6' -
0netstat -npt
-
Order and uniq
0declare -a array=($(tail -n +2 /proc/net/tcp | cut -d":" -f"3"|cut -d" " -f"1")) && for port in ${array[@]}; do echo $((0x$port)); done | sort | uniq -
0sudo netstat -plnt | grep :50 | awk '{print $7}' | awk -F/ '{print $1}' | xargs kill -9
- ‹ First < 3 4 5 6 7 >
What's this?
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.
Check These Out
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:
- » all commands
- » commands with 3 up-votes (commandlinefu3)
- » commands with 10 up-votes (commandlinefu10)
- » commands matching netstat