From: Ed W <lists@wildgooses.com>
To: "U.Mutlu" <for-gmane@mutluit.com>
Cc: netfilter@vger.kernel.org
Subject: Re: libiptc or alternative
Date: Mon, 07 Nov 2011 07:58:20 +0000 [thread overview]
Message-ID: <4EB78F9C.70907@wildgooses.com> (raw)
In-Reply-To: <j97eko$hs7$1@dough.gmane.org>
On 07/11/2011 02:09, U.Mutlu wrote:
>
> Hmm. I think in my case this method is suboptiomal because my
> iptables rules do change very frequently (ie. banning individual
> ip's at different times and then unbanning each after say x minutes,
> again individually, ie. not as a group).
>
> I think in this case I should stick with libiptc since it's still
> part of the official iptables distribution.
This is starting to sound like something ipset could help with?
Ed W
prev parent reply other threads:[~2011-11-07 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 20:14 libiptc or alternative U.Mutlu
2011-11-07 1:02 ` Pablo Neira Ayuso
2011-11-07 1:03 ` Pablo Neira Ayuso
2011-11-07 2:09 ` U.Mutlu
2011-11-07 7:58 ` Ed W [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=4EB78F9C.70907@wildgooses.com \
--to=lists@wildgooses.com \
--cc=for-gmane@mutluit.com \
--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