then mod_bw might solve it with the MaxConnection option :
.............
3.8 - MaxConnection [From] [Max]
This takes 2 parameters. From is the origin of the connections. It could
be a full host, part of a domain, an ip address, a network mask (i.e
192.168.0.0/24 or 192.168.0.0/255.255.255.0) or all.
The second parameter, is the max connections allowed from the origin.
Any
connection over Max, will get a 503 Service Temporarily Unavailable
There is a catch. You NEED to have a BandWidth limit for the same
origin.
It doesnt need to be a low limit. You can use an unlimited setting.
You might wonder why. It's because im using them same memory space of
the
bandwidth limit, to count the connections, so i can save memory space.
If you dont put a BandWidth using the same origin, MaxConnections will
be
ignored.
Example :
BandWidth all 0
MaxConnection all 20
or
BandWidth all 0
BandWidth 192.168.0.0/24 10240
MaxConnection all 20
MaxConnection 192.168.0.0/24 5
As for version 0.8, an user agent matching capability was introduced.
If you want to limit all clients using certain browser, you can limit
doing this :
MaxConnection u:[User-Agent] [Max]
User agent is a regular expression which will match the one sent by the
browser. This is easier to explain with examples :
Example :
MaxConnection "u:^Mozilla/5(.*)" 5
MaxConnection "u:wget" 5
First one, will match a browser that identifies itself as
Mozilla/5(etc)
Second one, will match a browser that has wget in any part of its id.
Please, rememeber that every speed, will depend mostly on your connection.
You cant get more speed if you dont have it.
Remember also.. if you dont follow the instructions, and get some weird
results, recheck your config before sending me an email.
.............
2007/12/23, Janne Jalkanen <[EMAIL PROTECTED]>:
>
>
> I took a look at cband already, but these solve the wrong problem,
> and would actually be harmful! They are really meant for the case
> where you want to make sure you're not moving too many bits (e.g.
> when you are paying for bandwidth). Limiting the bandwidth would
> just mean that *more* connections would be in-flight, since the guy
> will just start more connections when the bandwidth is low! That's
> how download accelerators work... So limitipconn is really the best
> option.
>
> /Janne
>
> On 23 Dec 2007, at 15:13, Harry Metske wrote:
>
> > Maybe you can have a look at mod_bw or mod_cband, both are
> > available for
> > Apache 2.x and offer bandwith throttling capabilities.
> >
> > regards,
> > Harry
> >
> > 2007/12/23, Janne Jalkanen <[EMAIL PROTECTED]>:
> >>
> >>
> >> Most of these, unfortunately, are only available for Apache 1.3 as
> >> packages, so I would need to compile by hand. I'll have to do it
> >> later, thanks!
> >>
> >> /Janne
> >>
> >> On 23 Dec 2007, at 01:22, Vlado Peshov wrote:
> >>
> >>> On Dec 22, 2007 10:32 PM, Janne Jalkanen <[EMAIL PROTECTED]>
> >>> wrote:
> >>>
> >>>>
> >>>> Fixed now. Instead of using apache config, I blocked the guy
> >>>> now at
> >>>> firewall level. If anyone has good tips on how to limit
> >>>> connections
> >>>> from a single IP address, let me know. Apache 2.0.x.
> >>>
> >>>
> >>> First thing from google:
> >>>
> >>> http://dominia.org/djao/limitipconn2.html
> >>>
> >>> I don't know for sure if this module is implemented in the standard
> >>> apache
> >>> installation.
> >>> Other useful modules for Apache:
> >>>
> >>> mod_throttle
> >>> mod_bandwidth
> >>> mod_load
> >>>
> >>> Like I have seen the server is running on ubuntu with Apache mod_jk
> >>> so it
> >>> will not be so difficult to install them directly from ubuntu
> >>> repositories.
> >>>
> >>> Regards, Vlado
> >>
> >>
> >
> >
> > --
> > met vriendelijke groet,
> > Harry Metske
> > Telnr. +31-548-512395
> > Mobile +31-6-51898081
>
>
--
met vriendelijke groet,
Harry Metske
Telnr. +31-548-512395
Mobile +31-6-51898081
