From: diab <lartc@diab.org>
To: lartc@vger.kernel.org
Subject: Re[2]: [LARTC] bandwidth limitation per dynamic IP
Date: Tue, 19 Oct 2004 10:54:30 +0000 [thread overview]
Message-ID: <1153439658.20041019125430@diab.org> (raw)
>> Is there a way to do the following with lartc tools :
>> I would like to limit any entering user to not use more than Xkb/mb to my
>> website. The IPs they use are changing all the time so static IP limitation
>> cannot be used. Is there a way doing so ?
OMH> You Say "any entering users"
OMH> If that case, then make a _general_ rule to throttle traffic from
OMH> to/from port 80
Or use apache to do it for you.. MOD_THROTTLE and MOD_BANDWIDTH is
your friend. I've been using mod_bandwidth successfully for limiting
traffic and it works perfectly.
Documentation here:
http://www.cohprog.com/v3/bandwidth/doc-en.html
MOD_THROTTLE docs here: http://www.snert.com/Software/mod_throttle/
-
diab
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-10-19 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 10:54 diab [this message]
2004-10-20 0:08 ` Re[2]: [LARTC] bandwidth limitation per dynamic IP Michael Slinn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1153439658.20041019125430@diab.org \
--to=lartc@diab.org \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.