From: "Joel Pearson" <pearj@writeme.com>
To: lartc@vger.kernel.org
Subject: RE: [general] Re: [LARTC] http bandwidth control
Date: Wed, 23 Jun 2004 11:54:42 +0000 [thread overview]
Message-ID: <000801c45918$e2117aa0$1b00a8c0@ROADLAP> (raw)
In-Reply-To: <1087956246.2423.2.camel@localhost.localdomain>
If you're only trying to limit http data use the squid proxy server with
delay pools:
My delay pools config for the squid proxy server:
acl only64kusers src 192.168.40.0/255.255.255.0
acl geoff src 192.168.40.198
acl joel src 192.168.40.188
acl ellen src 192.168.40.197
acl jonolaptop src 192.168.40.192
delay_pools 2
delay_class 1 3
delay_access 1 allow only64kusers !jonolaptop !geoff !ellen !joel
delay_access 1 deny all
delay_parameters 1 128000/128000 -1/-1 24000/24000
delay_class 2 3
delay_access 2 allow geoff ellen joel jonolaptop !only64kusers
delay_access 2 deny all
delay_parameters 2 192000/192000 -1/-1 192000/192000
This config mean that everyone except jonolaptop, geoff, ellen and joel is
restricted to a pool of 128 k/s where each connection can only use 24 k/s
And the next delay class means that jonolaptop, geoff, ellen and joel can
use 192 k/s all the time from a pool of 192 k/s
Hope it helps
-Joel
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] On
Behalf Of Jason Boxman
Sent: Wednesday, 23 June 2004 3:38 PM
To: lartc@mailman.ds9a.nl
Subject: [general] Re: [LARTC] http bandwidth control
On Tuesday 22 June 2004 22:04, Guillermo Gomez wrote:
> Hi
>
> I'm newbie on this and i would appreciate some pointers on how to limit
> the http trafic to my users from my linux-gateway box.
>
> Thanx in advance
--
Guillermo Gomez <ggomez@neotechgw.net>
neotech
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^^^^^^^^^^^^^^^^
Try the HOWTO?
--
Jason Boxman
Perl Programmer / *NIX Systems Administrator
Shimberg Center for Affordable Housing | University of Florida
http://edseek.com/ - Linux and FOSS stuff
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-06-23 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 2:04 [LARTC] http bandwidth control Guillermo Gomez
2004-06-23 5:38 ` Jason Boxman
2004-06-23 11:54 ` Joel Pearson [this message]
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='000801c45918$e2117aa0$1b00a8c0@ROADLAP' \
--to=pearj@writeme.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox