From: Weedy <weedy2887@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: best approach for blocklist
Date: Sat, 06 Mar 2010 02:11:16 -0500 [thread overview]
Message-ID: <4B920014.6030103@gmail.com> (raw)
In-Reply-To: <4B914406.1090306@chello.at>
Mart Frauenlob wrote:
> On 05.03.2010 17:17, netfilter-owner@vger.kernel.org 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?
There is a PDF I'm too lazy to google for about how the university of
florida mitigated a DDOS from a worm using TARPIT. Point being they had
to TARPIT hundreds of thousands of IPs and had to deal with the
performance issues behind that. It's a good read.
prev parent reply other threads:[~2010-03-06 7:11 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
2010-03-05 17:48 ` Mart Frauenlob
2010-03-06 7:11 ` Weedy [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=4B920014.6030103@gmail.com \
--to=weedy2887@gmail.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