[needs-packaging] libapache2-mod-limitipconn

The Apache 2 version is a port of the Apache 1.3 version. Therefore we should have two different packages :
- libapache-mod-limitipconn as already exists in Debian at http://packages.debian.org/etch/libapache-mod-limitipconn (built from http://dominia.org/djao/limitipconn.html)
- libapache2-mod-limitipconn that does not exist yet and should be built from http://dominia.org/djao/limitipconn2.html

i have done packaging this package:
http://revu.ubuntuwire.com/details.py?package=mod-limitipconn

During latest motu-release meeting, we decided to limit NEW packages for Jaunty to those which match features planned for the release. This could be material for Server team, subscribing Scott to have his opinion as Server team delegate, but I think it's better to wait Karmic or manage the upload in Debian directly to have this package autosynced.

Not for Jaunty.

Is there an update on the status of this bug?

wating from motu team

It seems libapache2-mod-bw package does the same job like apache2-mod-limitipconn

libapache2-mod-bw allows you to limit bandwidth usage on every virtual host/directory or to restrict the number of simultaneous connections. The limits can be configured according to the criteria:
 - origin of the connection,
 - file extension,
 - file size or
 - user agent of the client.

With libapache2-mod-bw you can restrict the number of simultaneous connections per vhost/dir and get some basic statistics info (tested version 0.91), so I'm asking: are in apache2-mod-limitipconn some feature, which doesn't exist in libapache2-mod-bw ?

Obviously the previous comment is very old, but I'm afraid it is based on a misunderstanding of the respective feature sets of mod_limitipconn and mod_bw.

mod_bw allows you to specify a collection of IP addresses, and a total aggregate limit on the number of connections allowed from that collection of addresses. For example, you can say "Serve no more than five simultaneous connections to the entire 192.168.2.0/24 address block."

mod_limitipconn by contrast allows you to specify an upper limit on the number of simultaneous connections that an arbitrary client IP address is allowed to open. With mod_limitipconn you can say "Serve no more than two simultaneous connections to any single IP address."

As far as I know there is NO way to duplicate the functionality of mod_limitipconn in mod_bw, short of enumerating each of the 2^32 possible IP addresses in your apache config file and configuring a connection limit for each address. If there was such a way, I wouldn't have written mod_limitipconn, because I tried for a long time to get mod_bw to do what I wanted.