Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Sven Schuster <schuster.sven@gmx.de>
To: Michael Schachtebeck <schachti@rbw.goe.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: limit extension
Date: Wed, 20 Jul 2005 17:15:43 +0200	[thread overview]
Message-ID: <20050720151543.GA15634@zion.homelinux.com> (raw)
In-Reply-To: <42DE65C6.6030504@rbw.goe.net>

[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]


Hi Michael,

On Wed, Jul 20, 2005 at 04:55:02PM +0200, Michael Schachtebeck told us:
> But on the other hand, the counter correctly shows the number of packets
> that matched the rule; iptables -t nat -vnL PREROUTING says:
> 
> 9 540 REDIRECT tcp -- eth1 * 10.10.10.69 0.0.0.0/0 tcp spts:1024:65535
> dpt:80 flags:0x16/0x02 limit: avg 1/day burst 1 redir ports 5000
> 
> So it would be very strange if the rules were extracted to user space,
> rewritten/modified, "uploaded" to the kernel with the correct counters
> for the remaining rules, and then, the rules do not look to this
> counters. ;-)

I'm not that familiar with the iptables internals, but I suspect that
the counters (which are probably part of the "core" rule data structure)
are downloaded to userspace and get uploaded again untouched when just
adding or deleting a rule from an existing ruleset, but the limit-match
internal data structure will will get reallocated.

Maybe one of the developers reads this mail and can prove me wrong or
perhaps even right :-)



Sven

> 
> Why then save and restore the counters, if they are not used by the rules?
> 
> Michael.

-- 
Linux zion 2.6.13-rc3-mm1 #6 PREEMPT Mon Jul 18 19:42:52 CEST 2005 i686 athlon i386 GNU/Linux
 17:11:17 up 1 day, 21:23,  1 user,  load average: 0.00, 0.05, 0.05

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-07-20 15:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 18:07 limit extension Michael Schachtebeck
2005-07-19 20:13 ` Jan Engelhardt
2005-07-19 21:01   ` Michael Schachtebeck
2005-07-20  6:25     ` Jan Engelhardt
2005-07-20 14:15 ` Michael Schachtebeck
2005-07-20 15:01   ` Sven Schuster
2005-07-20 15:03     ` Michael Schachtebeck
2005-07-20 15:05       ` Jan Engelhardt
     [not found]   ` <20050720144531.GA14941@zion.homelinux.com>
     [not found]     ` <42DE65C6.6030504@rbw.goe.net>
2005-07-20 15:15       ` Sven Schuster [this message]

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=20050720151543.GA15634@zion.homelinux.com \
    --to=schuster.sven@gmx.de \
    --cc=netfilter@lists.netfilter.org \
    --cc=schachti@rbw.goe.net \
    /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