From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: viewing rules and traffic while inserting/removing rules
Date: Thu, 08 May 2008 11:44:07 -0500 [thread overview]
Message-ID: <48232DD7.3070603@riverviewtech.net> (raw)
In-Reply-To: <090801c8b07c$fa084b60$5000040a@skathlaptop>
On 05/07/08 15:01, Steven Kath wrote:
> Have you considered using netfilter's ip sets for this? Sounds like
> it might be perfect for your needs.
With out knowing how or what the OP is accounting we don't know if s/he
is looking at each individual network that is being filtered or if it is
clients behind the system. If it is networks that are being filtered I
would think that the single ipset rule would make it much harder, if not
impossible, to keep accounting data for a single rule.
Grant. . . .
next prev parent reply other threads:[~2008-05-08 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 17:26 viewing rules and traffic while inserting/removing rules lists+netfilter
2008-05-07 18:25 ` Jan Engelhardt
2008-05-07 20:01 ` Steven Kath
2008-05-07 21:29 ` lists+netfilter
2008-05-08 16:44 ` Grant Taylor [this message]
2008-05-08 17:17 ` lists+netfilter
2008-05-08 19:21 ` Grant Taylor
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=48232DD7.3070603@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox