From: David Gubler <dg@doodle.com>
To: netfilter@vger.kernel.org
Subject: Re: connlimit reached - cannot open connections even after I close some
Date: Thu, 24 Jan 2013 16:08:15 +0100 [thread overview]
Message-ID: <51014E5F.9070804@doodle.com> (raw)
In-Reply-To: <77346cbd-787d-4e7e-a918-d1b858d56b25@me.com>
Hi Bryan,
> I would think you could approach the problem by using apache's builtin
> rate limiting function,
Yes we're using Apache and I researched that as well, but:
First, I'm thinking that an Apache module cannot reliably enforce a
connection limit - after all, the module can only act *after* the
connection has been established.
Second, I have not found an apache module that is included in Debian
(required for automatic security updates) and is able to do that.
* mod_limitipconn is not available for Debian (it seems)
* mod_bw cannot limit connections per IP, only per scope
* mod_evasive counts hits on an object, not parallel connections
However, if you can point me to one I would give it a try anyway.
And after all, it really bugs me that apparently connlimit is supposed
to do what I want, but shows this erratic behavior...
David
--
David Gubler
Senior Software & Operations Engineer
MeetMe: http://doodle.com/david
E-Mail: dg@doodle.com
next parent reply other threads:[~2013-01-24 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <77346cbd-787d-4e7e-a918-d1b858d56b25@me.com>
2013-01-24 15:08 ` David Gubler [this message]
[not found] ` <CAHn-yPwtNh6sSo0PMScgavbgS=5mmLGaUHmQrj4wJQxMj4pWpA@mail.gmail.com>
2013-01-28 16:17 ` connlimit reached - cannot open connections even after I close some David Gubler
2013-01-24 14:22 David Gubler
2013-02-03 11:51 ` Pascal Hambourg
2013-02-04 11:29 ` David Gubler
2013-02-05 19:54 ` Pascal Hambourg
2013-02-11 12:44 ` David Gubler
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=51014E5F.9070804@doodle.com \
--to=dg@doodle.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