Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Marek Kierdelewicz <marek@piasta.pl>
To: "J. Bakshi" <joydeep@infoservices.in>
Cc: netfilter@vger.kernel.org
Subject: Re: How to protect apache benchmarking attack ?
Date: Tue, 12 Jan 2010 10:28:48 +0100	[thread overview]
Message-ID: <20100112102848.4b427416@catlap> (raw)
In-Reply-To: <4B4C3F37.9010703@infoservices.in>

>Hello all,

Hello J.,

>I am dared to see what "ab" (apache benchmarking too) can do  against
>an apache server.  I have used the following against my server to check
>call handling

You can use hashlimit [1] match of iptables to limit concurrent
connections from single IP.

[1] http://linux.die.net/man/8/iptables -> lookup hashlimit; note:
current versions of hashlimit can also use srcip as --hashlimit-mode;
that's probably what you want

Cheers,
Marek Kierdelewicz

  reply	other threads:[~2010-01-12  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12  9:21 How to protect apache benchmarking attack ? J. Bakshi
2010-01-12  9:28 ` Marek Kierdelewicz [this message]
2010-01-12  9:40   ` J. Bakshi
2010-01-12 10:03     ` J. Bakshi
2010-01-12 11:08       ` [ Siccess ]How " J. Bakshi

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=20100112102848.4b427416@catlap \
    --to=marek@piasta.pl \
    --cc=joydeep@infoservices.in \
    --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