All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 6/10][CTNETLINK] dump counters iif connection ended or counters filled up
Date: Fri, 07 Jul 2006 15:51:06 +0200	[thread overview]
Message-ID: <44AE66CA.8030705@netfilter.org> (raw)
In-Reply-To: <44ADE7BA.4030406@trash.net>

Patrick McHardy wrote:
> Pablo Neira Ayuso wrote:
> 
>>This patch makes ctnetlink to dump counters iif connection reaches the
>>destroy state or altenatively if counters filled up.
>>
>>AFAICS counters on NEW and UPDATE events doesn't provide interesting
>>information, they just consume the limited netlink bandwidth.
>>
>>Upcoming conntrackd release in statistics mode uses counters from
>>DESTROY events to keep the contability of traffic that the firewall has
>>processed.
>>
>>I think that this patch should also reset counters upon fill up event,
>>comments?
> 
> Not sure, do you know any users of the counters besides conntrackd?

I don't know any ctnetlink user of the counters. Thinking it well this 
"counters fill up" issue is tricky. Since netlink is unreliable, what if 
the fill up event gets lost? we could reset counters and nobody would 
apparently notice. I think that we need an overflow bit in the conntrack 
that must be set whenever and overflow happens and unset such bit once 
the overflow event has been caught.

-- 
The dawn of the fourth age of Linux firewalling is coming; a time of 
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris

  parent reply	other threads:[~2006-07-07 13:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07  2:15 [PATCH 6/10][CTNETLINK] dump counters iif connection ended or counters filled up Pablo Neira Ayuso
2006-07-07  4:48 ` Patrick McHardy
2006-07-07  8:25   ` Amin Azez
2006-07-07 13:51   ` Pablo Neira Ayuso [this message]
2006-07-07 16:03     ` Amin Azez
2006-07-10  4:47     ` Patrick McHardy
2006-07-13 20:09       ` Pablo Neira Ayuso
2006-07-14  9:43         ` Patrick McHardy
2006-07-07  8:18 ` Amin Azez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44AE66CA.8030705@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.