From: Radek Kanovsky <rk@dat.cz>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter@vger.kernel.org
Subject: Re: iptables rules in comparable form
Date: Tue, 1 Jun 2010 21:36:29 +0200 [thread overview]
Message-ID: <20100601193629.GC19088@q.uh.cz> (raw)
In-Reply-To: <alpine.LSU.2.01.1006012020370.15461@obet.zrqbmnf.qr>
On Tue, Jun 01, 2010 at 08:26:30PM +0200, Jan Engelhardt wrote:
> Sounds like you need xt_quota2. As its counters are independent of
> rules when given names, they can never get set back to a value
> less than what they were.
I wanted to avoid any nonstandard packages but this looks promissing.
I will take a look. Thanks.
> As I said before, there is no concept of unchanged rules.
>
> When you iptables -A, the entire ruleset is fetched from the kernel,
> then modified, and finally reinserted - even when having only
> added a single rule.
But I have scalability problems even if there is declared O(N)
complexity of iptables-restore. There is a really big difference
if counters are reset at 9:14:01 or at 9:14:53. I am not sure
what COMMIT during restoration exactly do but can't it be
used for tuning in such cases?
Radek Kanovsky
next prev parent reply other threads:[~2010-06-01 19:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 8:10 iptables rules in comparable form Radek Kanovsky
2010-06-01 8:50 ` Jan Engelhardt
2010-06-01 9:18 ` Mart Frauenlob
2010-06-01 11:25 ` Radek Kanovsky
2010-06-01 11:56 ` Jan Engelhardt
2010-06-01 16:03 ` Radek Kanovsky
2010-06-01 18:19 ` Jan Engelhardt
2010-06-01 18:35 ` Radek Kanovsky
2010-06-01 18:01 ` Radek Kanovsky
2010-06-01 18:26 ` Jan Engelhardt
2010-06-01 19:36 ` Radek Kanovsky [this message]
2010-06-01 20:29 ` Pieter Smit
2010-06-02 6:17 ` Radek Kanovsky
2010-06-01 13:27 ` Mart Frauenlob
2010-06-01 16:47 ` Radek Kanovsky
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=20100601193629.GC19088@q.uh.cz \
--to=rk@dat.cz \
--cc=jengelh@medozas.de \
--cc=netfilter@vger.kernel.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.