From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shaping traffic by flows
Date: Tue, 13 May 2003 17:15:36 +0000 [thread overview]
Message-ID: <marc-lartc-105284685528927@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105284563727431@msgid-missing>
On Tuesday 13 May 2003 18:47, Michael Ulitskiy wrote:
> Hi,
>
> I'm not sure if this question already came up in this list, but
> I seem to be unable to find an answer for it.
> I have a server and a few thousand of clients that can access
> the server. I would like to setup a traffic shaping such a way
> that each particulat client is given a particular bandwith.
> Let's say each client (clients differentiated by ip address) is
> allowed to use no more than 100kbit of download bandwith.
> So it is my understanding that traffic should be differentiated
> by flows and each flow should be given a particular bandwith
> with any queueing discipline available. The question is how to
> do it.
> I can't figure out a way to accomplish it except writing thousands
> of filtering rules for each ip and also thousands classes for them.
> I probably can use hashing filters but it wouldn't eliminate
> thousands of classes each with the same shaping rate.
> So once again the question is whether it's possible to shape each
> flow from a particular ip range to the particular rate?
Not without creating a lot of classes. You can try the wrr qdisc :
http://wipl-wrr.sourceforge.net/
It creates 1 class for each ip-addres (or mac-address) it sees.
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:[~2003-05-13 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 16:47 [LARTC] Shaping traffic by flows Michael Ulitskiy
2003-05-13 17:15 ` Stef Coene [this message]
2003-05-13 18:28 ` Michael Ulitskiy
2003-05-13 20:13 ` Matias Bjorling
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-105284685528927@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 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.