[pfSense] rate limiting

[Nathan Eisenberg]

Not at an HTTP layer.  You could limit the maximum state entries per host to 100, and set the state timeout to 60, but then all connections (to any file) will be limited in that way.

This kind of rule belongs either at an HTTP proxy layer (if you were to frontend your website with haproxy or ngnix) or in the application itself.
Nathan Eisenberg
Atlas Networks | Sr. Systems Administrator
office: 206.577.3078  |  www.atlasnetworks.us<http://www.atlasnetworks.us/>
[Description: Description: Description: Description: FaceBook-icon]<http://www.facebook.com/AtlasNetworks> [Description: Description: Description: Description: Twitter-icon] <http://twitter.com/atlasnetworks>

From: list-bounces at lists.pfsense.org [mailto:list-bounces at lists.pfsense.org] On Behalf Of S Ahmed
Sent: Monday, January 23, 2012 11:20 AM
To: list at lists.pfsense.org
Subject: [pfSense] rate limiting

Does pfsense support rate limit for the given scenerio:

Clients use a API that sends http post requests to my server at a specific url like:

www.example.com/some_service/a/b<http://www.example.com/some_service/a/b>


I want to limit the # of requests per minute to 100.

If there are more than 100 requests in a given minute, I want to hard block all further requests.

I don't know client i.p addresses before hand.

Also if this is possible, could I also set different rate limits if I knew the clients ipaddress/server host?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pfsense.org/pipermail/list/attachments/20120123/714c608b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1075 bytes
Desc: image001.png
URL: <http://lists.pfsense.org/pipermail/list/attachments/20120123/714c608b/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1114 bytes
Desc: image002.png
URL: <http://lists.pfsense.org/pipermail/list/attachments/20120123/714c608b/attachment-0003.png>