Comments on: Lighttpd Traffic Shaping: Throttle Connections Per Single IP (Rate Limit)

By: JC

JC — Sat, 22 Oct 2011 08:44:05 +0000

There is mod_evasive for Apache.

By: David

David — Sun, 18 Sep 2011 20:49:18 +0000

Excelent, but is there a way you can do the same using apache instead of lighthttp?

By: Vivek Gite

Vivek Gite — Sun, 12 Jun 2011 09:38:58 +0000

You serve all static content (css/js/images/videos) from other domain or cdn to avoid this issue.

By: dirk

dirk — Fri, 18 Mar 2011 12:11:30 +0000

evasive.max-conns-per-ip = 14
is a good value for lighttpd. no need to install firewalls.

By: gadelkareem

gadelkareem — Sat, 28 Aug 2010 14:49:41 +0000

What about evasive.max-conns-per-ip = 20 for lighty?

By: gadelkareem

gadelkareem — Sat, 28 Aug 2010 14:46:47 +0000

could you give up an example?

By: The Mikeness

The Mikeness — Wed, 21 Jul 2010 21:55:26 +0000

Note that limiting concurrent connections per IP to 100 may block some organizations that use a shoddy HTTP Proxy, as it will usually refuse to hold persistent connections, and there may be dozens or hundreds of users behind the proxy. What the end users will begin to see if you do alot of this sort of filtering without using extreme care is things failing at odd places, too many requests within a few seconds randomly causing some portions of pages to not load completely (like CSS and image files), AJAX requests to fail, etc.

I just though I’d mention that incase this sort of thinking becomes prominent among people running webservers and big sites start to have hard to troubleshoot problems that may end up ruining your reputation amongst your users for being unable to operate a reliable service.

By: Vicent Gonzalez i Castells

Vicent Gonzalez i Castells — Wed, 12 Aug 2009 07:01:09 +0000

Great job. A good information.

Following Swapnil comment, it’s a great problem to create a white list. We can think about to create a white list of universitues IP’s of the world. For me, it’s a good technique to apply into small environments like a enterprise network.

Santi

By: geeth

geeth — Mon, 03 Aug 2009 12:14:22 +0000

The blog is really superb stuff, could you please mention the regarding apache module too

By: kunal

kunal — Thu, 25 Jun 2009 02:58:21 +0000

Thanks Vivek,

Will definitely give a try to this.

-
Kunal

By: Vivek Gite

Vivek Gite — Wed, 24 Jun 2009 05:20:03 +0000

Try,
mod_bandwidth:

“Mod_bandwidth” is a module for the Apache webserver that enable the setting of server-wide or per connection bandwidth limits, based on the directory, size of files and remote IP/domain.

Download : http://www.cohprog.com/mod_bandwidth.html
mod_limitipconn:

It allows web server administrators to limit the number of simultaneous downloads permitted from a single IP address.

Download : http://dominia.org/djao/limitipconn2.html

By: kunal

kunal — Wed, 24 Jun 2009 04:47:06 +0000

How can i throttle connections per single IP in apache. Earlier there used to be a module named as mod_evassive but now i dont think its available any more.

–
Kunal

By: Vivek Gite

Vivek Gite — Mon, 22 Jun 2009 08:36:07 +0000

You can always white list certain IPs / subnets or create class of IPs to exclude throttling.

By: Swapnil K. Chaudhari

Swapnil K. Chaudhari — Mon, 22 Jun 2009 06:08:36 +0000

Hi,
I have a query regardig Limiting Connections Per Single IP.

Cosider a scenario of a big company, where there is only one public IP address available and all the users use DHCP or private IP. So if say 100 emplyee in the company access the same web site simultaneously (For checking mails, or some other common information). Web server will see that same public IP is generating 100 connections and put the public IP of company in black list, and employees won’t be able to connect to that web server.

How can we avoid this scenario?

Thanks,
Swapnil.

By: Vasi

Vasi — Mon, 22 Jun 2009 03:13:16 +0000

Excellent information thanks a lot