[Eug-lug] Bandwidth limiting for apache2?

[Allen Brown]

I think I read an article in Linux Journal about the Linux Firewall
introduced in 2.4 that talked about doing this.  I think doing
this at the firewall level would be the best approach because
it would have lower overhead than any other approach.
--
Allen Brown
  work: Agilent Technologies      non-work: http://www.peak.org/~abrown/
        allen_brown at agilent.com             abrown at peak.org
  The dinosaurs became extinct because they didn't have a space program.
  --- Larry Niven


On Sat, 22 Jan 2005, larry price wrote:

> google isn't giving me any love on this one.
> 
> II'm trying to limit bot attacks against a webserver.
> 
> I'm looking for a way to cap requests on a per ip basis,
> but don't want to block legitimate requests at all,
> I also want to be able to automatically detect, record, and block new attacks.
> 
> I was looking at mod_throttle and mod_bandwidth but they are strictly for 1.3
> 
> Is this a problem that is better dealt with at the packet filtering level?
> 
> would it be worthwhile to attempt to port one of the aforementioned
> modules to apache 2.0 ?
> 
> It's more important that requests be limited than that total outgoing
> bandwidth be limited and I have no problem with returning a 403 error
> to offending requests.
> 
> Suggestions? Comments? Places to look for more docs.?
> 
> -- 
> http://Zoneverte.org -- information explained
> Do you know what your IT infrastructure does?
> _______________________________________________
> EUGLUG mailing list
> euglug at euglug.org
> http://www.euglug.org/mailman/listinfo/euglug
>