From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Krzysztof Oledzki <ole@ans.pl>,
Holger Eitzenberger <holger@eitzenberger.org>,
pablo@netfilter.org,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: nf_conntrack.acct has no effect
Date: Tue, 17 Mar 2009 15:41:32 +0100 [thread overview]
Message-ID: <49BFB69C.6030004@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0903171535210.3657@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> xt_conntrack for example has a nicer effect: once you add a rule that
> contains it, it will load nf_conntrack_ipv{4,6}, which in turn causes
> Netfilter to start tracking in the first place.
>
> So along the lines, xt_connbytes could pin a module (or perhaps
> something more light-weight) to ultimately signify
> "forced-activation"/"deactivation-impossible", much like you cannot
> remove nf_conntrack while an xt_conntrack-using rule is in place.
It doesn't have to be forced IMO, but yes, the automatic enabling
should be similar to what xt_conntrack does.
> Then only one thing remains. As for nf_conntrack, once it is loaded,
> it picks up already-running connections (and loses them as soon
> as you rmmod it). This is not the case with accounting as far as I
> have observed yesterday - only new connections get to have (or
> not to have) an acct structure; existing ones are not modified
> or picked up like conntrack does.
Thats not possible using ct_extend.
next prev parent reply other threads:[~2009-03-17 14:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 16:53 nf_conntrack.acct has no effect Jan Engelhardt
2009-03-16 16:56 ` Patrick McHardy
2009-03-16 18:01 ` Jan Engelhardt
2009-03-17 8:24 ` Holger Eitzenberger
2009-03-17 13:02 ` Patrick McHardy
2009-03-17 13:13 ` Krzysztof Oledzki
2009-03-17 13:31 ` Patrick McHardy
2009-03-17 13:32 ` Patrick McHardy
2009-03-17 13:50 ` Krzysztof Oledzki
2009-03-17 13:51 ` Patrick McHardy
2009-03-17 13:55 ` Krzysztof Oledzki
2009-03-17 13:57 ` Patrick McHardy
2009-03-17 14:18 ` Krzysztof Oledzki
2009-03-17 14:22 ` Patrick McHardy
2009-03-17 14:36 ` Krzysztof Oledzki
2009-03-17 14:38 ` Patrick McHardy
2009-03-17 13:11 ` Krzysztof Oledzki
2009-03-17 13:28 ` Jan Engelhardt
2009-03-17 13:52 ` Krzysztof Oledzki
2009-03-17 13:54 ` Patrick McHardy
2009-03-17 14:39 ` Jan Engelhardt
2009-03-17 14:41 ` Patrick McHardy [this message]
2009-03-17 15:41 ` Jan Engelhardt
2009-03-18 4:32 ` Patrick McHardy
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=49BFB69C.6030004@trash.net \
--to=kaber@trash.net \
--cc=holger@eitzenberger.org \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=ole@ans.pl \
--cc=pablo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox