From: Mike Wright <mike.wright@mailinator.com>
To: "Dennis J." <dennisml@conversis.de>
Cc: netfilter@vger.kernel.org
Subject: Re: best approach for blocklist
Date: Fri, 05 Mar 2010 09:43:28 -0800 [thread overview]
Message-ID: <4B9142C0.5010208@mailinator.com> (raw)
In-Reply-To: <4B912EA0.1060604@conversis.de>
Dennis J. wrote:
> Hi,
> I'm wondering what the most efficient way to implement a blocklist is.
> We are basically talking about blocking a few thousand IPs. Does
> iptables do some internal optimizations when blocking based on a source
> address or would it be better to, say, create a chain for each class A
> net (e.g. 83.0.0.0/8) and then add the IPs in that range to that class
> to make the matching more efficient?
Have you considered ipset? I use it in various ways, sometimes to
allow, sometimes to deny. It supports IPs, NETs, ports, etc.
next prev parent reply other threads:[~2010-03-05 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 16:17 best approach for blocklist Dennis J.
2010-03-05 17:11 ` Payam Chychi
2010-03-05 17:43 ` Mike Wright [this message]
2010-03-05 17:48 ` Mart Frauenlob
2010-03-06 7:11 ` Weedy
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=4B9142C0.5010208@mailinator.com \
--to=mike.wright@mailinator.com \
--cc=dennisml@conversis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox