[SAC] [OSGeo] #216: Fighting Bandwidth Accelerators

Committees SAC mailing list
1

#216: Fighting Bandwidth Accelerators
----------------------+-----------------------------------------------------
Reporter: warmerdam | Owner: sac@lists.osgeo.org
    Type: task | Status: new
Priority: normal | Component: SAC
Keywords: |
----------------------+-----------------------------------------------------
It would be helpful to have a strategy to limit bandwidth accelerators.
That is, situations where one IP open many connections, often on the same
file - in an apparent attempt to download it quickly. In some cases this
seems to be misconfigured and result in repeated downloads, and in other
cases it just ties up a lot of server slots, potentially denying other
users service.

One suggestion has been to use mod_cband to limit bandwidth, but this
doesn't really stop multiple connections at once, and might limit
legitimate high bandwidth use. A also, the mod_cband site
(http://cband.linux.pl) does not seem to be available.

Another promising looking option is mod_limitipconn:

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

--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/216&gt;
OSGeo <http://www.osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

2

#216: Fighting Bandwidth Accelerators
---------------------------+------------------------
Reporter: warmerdam | Owner: warmerdam
     Type: task | Status: reopened
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+------------------------

Comment (by TemptorSent):

Modern browsers and download agents utilize far more connections than they
did when this bug was opened. If connection limits are really necessary,
they should be set to at the very least 8, but preferably eliminated
entirely and serious abuse handled at the network layer. If it's
specifically downloads of large files that is causing concern, limits
should be imposed only with that specific scope and/or a better means for
handling very large files should be identified and implemented.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/216#comment:8&gt;
OSGeo <http://www.osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.