limitipconn is a tool which is used to limit the number of connections per IP on our server. This tool can help in lowering the load on your server if someone connecting too many times from the same IP.
First we need to download the file.
#tar -xjf mod_limitipconn-0.23.tar.bz2
Now, we are compile the module into Apache using:
#/usr/local/apache/bin/apxs -cia mod_limitipconn.c
Update the httpd.conf file using this command:
Edit the file using vim or vi
Lets add in the following lines to the bottom of the file:
# Set a server-wide limit of 10 simultaneous downloads per IP,
# no matter what.
# This section affects all files under http://your.server/somewhere
# exempting images from the connection limit is often a good
# idea if your web page has lots of inline images, since these
# pages often generate a flurry of concurrent image requests
# This section affects all files under /home/*/public_html
# In this case, all MIME types other than audio/mpeg and video*
# are exempt from the limit check
OnlyIPLimit audio/mpeg video
Now edit the file /usr/local/apache/conf/includes/pre_main_global.conf and add the following lines
Now restart apache
You can check whether the module loaded or not using the following command.
/usr/local/apache/bin/httpd -M | grep limitipconn_module
1) This module will not function unless mod_status is loaded and the
“ExtendedStatus On” directive is set.
2) Server-wide access restrictions and per-directory access restrictions
are computed separately. In the above example, if someone is
downloading 11 images from http://your.server/somewhere
simultaneously, they WILL be denied on the 11th download, because the
server-wide limit of 10 downloads is not affected by the per-directory
NoIPLimit. If you want to set global settings which can be overruled
by per-directory settings, you will need something like
# global per-directory settings here
# local per-directory settings here
3) If you are using any module based upon a quick handler hook (such as
mod_cache), mod_limitipconn will not be able to process any
per-directory configuration directives in time to affect the return
result of the other module. This is a technical limitation imposed
by Apache. In such a situation, you will have to use server-wide
configuration directives only.
Note that previous versions of mod_limitipconn did not allow any
server-wide configuration directives, and hence could not be used
with mod_cache at all. In other words, the present situation still
represents an improvement over previous versions.
4) The limits defined by mod_limitipconn.c apply to all IP addresses
connecting to your Apache server. Currently there is no way to set
different limits for different IP addresses.
5) Connections in excess of the limit result in a stock 503 Service
Temporarily Unavailable response. The job of returning a more useful
error message to the client is left as an exercise for the reader.
6) mod_limitipconn sets the LIMITIP environment variable to 1 whenever a
download is denied on the basis of too high an IP count. You can use
this variable to distinguish accesses that have been denied by this
module. For example, a line like
CustomLog /var/log/httpd/access_log common env=!LIMITIP
in httpd.conf can be used to suppress logging of denied connections
from /var/log/httpd/access_log. (Note that, if you really want to
suppress logging, you’ll probably also want to comment out the
ap_log_rerror lines from mod_limitipconn.c as well.)
7) By default, all clients behind a proxy are treated as coming from the
proxy server’s IP address. If you wish to alter this behavior,
consider installing mod_extract_forwarded from