Show all listening and established ports TCP and UDP together with the PID of the associated process

netstat -plantu
Easy to remenber. Fot TCP only use: netstat -plant
Sample Output
[root@server ~]# netstat -plantu
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
tcp        0      0    *                   LISTEN      13696/Xvnc
tcp        0      0       *                   LISTEN      2161/rpcbind
tcp        0      0     *                   LISTEN      2350/rpc.statd
tcp        0      0      *                   LISTEN      13696/Xvnc
tcp        0      0        *                   LISTEN      2584/sshd
tcp        0      0     *                   LISTEN      2461/cupsd
tcp        0      0      *                   LISTEN      2678/master
tcp        0      0      *                   LISTEN      2733/qpidd
tcp        0     52             ESTABLISHED 13889/sshd
udp        0      0     *                               2332/avahi-daemon
udp        0      0       *                               2350/rpc.statd
udp        0      0     *                               2350/rpc.statd
udp        0      0      *                               2332/avahi-daemon
udp        0      0       *                               2080/portreserve
udp        0      0       *                               2161/rpcbind
udp        0      0       *                               2461/cupsd
udp        0      0       *                               2161/rpcbind

By: player27
2012-01-19 00:18:43

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: