Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
  • Ubuntu Server 10.04.1 x86
  • Munin 1.4.4

Here is what Munin tells me about connections through firewall on my server:


Here is what netstat -n has to say about this:

$ netstat -an|awk '/tcp/ {print $6}'|sort|uniq -c
      2 CLOSE_WAIT
      1 CLOSING
     34 FIN_WAIT1
     21 FIN_WAIT2
     13 LAST_ACK
      6 LISTEN
      4 SYN_RECV
    394 TIME_WAIT

According to netstat, 10% of sockets are in TIME_WAIT; 75% or more, according to Munin.

That is strange. Who is right?

More details about configuration etc. here: How to reduce number of sockets in TIME_WAIT?

share|improve this question
Munin looks at /proc/net/ip_contrack. Indeed, it reports 19K connections in TIME_WAIT out of total 20K. The question is, who to believe? – Alexander Gladysh Dec 13 '10 at 21:47
Or am I trying to compare apples with oranges? If so, which Munin graph should I use? – Alexander Gladysh Dec 13 '10 at 21:57
Link down............ – Pacerier Jan 23 at 3:42
up vote 4 down vote accepted

netstat doesn't show connections that are passing through the server as a gateway / firewall.

The munin-plugin parses /proc/net/ip_conntrack, which contains a lot of information not visible in netstat.

The answer; Both are right, but they answer different questions. Netstat talks about connections to and from the server itself. Conntrack provides information about traffic passing the server, so it can make sure to do address translation and so forth correctly.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.