From: Frank Smith <fsmith@hoovers.com>
To: Daniel David Benson <dan@spoontail.com>, netfilter@lists.netfilter.org
Subject: Re: Connection Rate Limiting
Date: Thu, 15 May 2003 11:31:24 -0500 [thread overview]
Message-ID: <43210000.1053016283@hoovers-59.hoovers.com> (raw)
In-Reply-To: <Pine.GSO.4.44.0305150852190.7322-100000@dudester.spoontail.com>
I use this to rate-limit spiders:
iptables -A FORWARD -p tcp -s xxx.xxx.xxx.xxx --dport 80 -m limit --limit 20/m -j ACCEPT
Frank
--On Thursday, May 15, 2003 08:58:25 -0700 Daniel David Benson <dan@spoontail.com> wrote:
>
> Hopefully this one hasn't been answered before. We need to rate
> limit on a per source IP address to port 80. We are seeing certain
> web servers suffer from resource starvation under a DDOS attack.
> The solution to this problem is rate limit the number of
> connections any source IP address can make. Is this possible
> to do with iptables? I have searched just about everything and
> I can't seem to find anything. I know I can do traffic shaping
> with iproute2, but I don't think that is the direction I want
> to take.
>
> I know there is -limit in iptables, but unless I don't clearly
> understand the implementation this limit is matched against
> the resource and not on a per source. So, you have 5 source
> IPs comming in with requests all of which effect the counters
> global instead of each source having their own counter.
>
> We have tried mod_throttle for apache...but that crashes quite
> a bit as the tables grow. Plus. I want to stop the attacks
> before the apache level.
>
> Any help on this would be greatly appreciated.
>
> Thanks!
>
> -Dan
>
>
--
Frank Smith fsmith@hoovers.com
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
next prev parent reply other threads:[~2003-05-15 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 15:58 Connection Rate Limiting Daniel David Benson
2003-05-15 16:31 ` Frank Smith [this message]
2003-05-15 19:15 ` Tomas Edwardsson
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=43210000.1053016283@hoovers-59.hoovers.com \
--to=fsmith@hoovers.com \
--cc=dan@spoontail.com \
--cc=netfilter@lists.netfilter.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