From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] traffic control based on the downloaded bytes
Date: Wed, 06 Nov 2002 17:04:01 +0000 [thread overview]
Message-ID: <marc-lartc-103660261508837@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103657740713718@msgid-missing>
On Wednesday 06 November 2002 11:09, Gabor Csuri wrote:
> Hi All,
>
> I'm new on this list. I'm the admin of the server in our house.
> We have a 768k/128k DSL line.
> There are 11 flats using this bandwith without any control.
> Some of them are "high donwloader" and the browsing speed is decreasing a
> lot when the downloaders are waken up. :(
> I have an idea how the downloaders and the browsers can use this bandwith
> without any conflict.
> My question is: Is it possible with iproute2 ?
> My idea: I define a bandwith to downloaders (maybe 512k).
> If any of the downloading thread exceed a limit (maybe 4Mbyte) it passed
> into the 512k bandwith.
> How can I do this trick?
There is a length match in iptables. But I don't know if it will work.
You can also use squid and uses the delay pools in squid.
But why don't you put all the bandwidth eating traffic in 1 class and give it
a lower bandwith? If there is no other traffic, they can use the full link,
but if there is other traffic, other traffis is served first.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-06 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 10:09 [LARTC] traffic control based on the downloaded bytes Gabor Csuri
2002-11-06 17:04 ` Stef Coene [this message]
2002-11-06 19:49 ` Gabor Csuri
2002-11-06 20:06 ` Stef Coene
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=marc-lartc-103660261508837@msgid-missing \
--to=stef.coene@docum.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox