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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/145065 Title: [needs-packaging] libapache2-mod-limitipconn To manage notifications about this bug go to: https://bugs.launchpad.net/hardy-backports/+bug/145065/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
