From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: RV: [LARTC] Re: My 1st BW Manager
Date: Mon, 21 Apr 2003 09:12:03 +0000 [thread overview]
Message-ID: <marc-lartc-105091660616965@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105074710025619@msgid-missing>
On Monday 21 April 2003 04:30, Martin A. Brown wrote:
> Rio,
>
> : I give you real situation in my network:
> :
> : eth0[PUBLIC.IP]
> : LINUX - BW - Manager
> : eth1[192.168.1.10]
> :
> :
> : 4 hosts: 192.168.1.1 - 192.168.1.4
> :
> : My total bandwidth is only 128Kbit
> : All NICs are Realtek 10Mbit
> :
> : So the solution as you offered is to put each class 128Kbit/4 = 32Kbit?
> : If that so, then it would be good if i use CBQ qdisc, not HTB. I want to
> : use HTB because HTB burstable.
>
> I would suggest the following configuration (as Stef has proposed):
>
> 128kbit ceil 128kbit +---- rate 32kbit ceil 128kbit <-- 192.168.1.1
>
> +---------------+---- rate 32kbit ceil 128kbit <-- 192.168.1.2
>
> +---- rate 32kbit ceil 128kbit <-- 192.168.1.3
>
> +---- rate 32kbit ceil 128kbit <-- 192.168.1.4
>
> Now, you have four different classes, one for each IP. Each IP is
> guaranteed 128kbit.
Each IP Is guaranteed 32 kbit, not 128 kbit.
> Each IP can consume up to 128kbit, if there isn't
> competition with other classes.
>
> You should use the qdisc with which you are most comfortable--both CBQ and
> HTB can do this for you. For reference, it seems that the experience on
> this list leans toward HTB, though.
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-04-21 9:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 10:10 RV: [LARTC] Re: My 1st BW Manager GoMi
2003-04-19 12:01 ` Stef Coene
2003-04-19 13:53 ` GoMi
2003-04-19 14:36 ` Stef Coene
2003-04-19 15:19 ` rio
2003-04-20 21:51 ` Stef Coene
2003-04-21 1:59 ` rio
2003-04-21 2:30 ` Martin A. Brown
2003-04-21 3:12 ` rio
2003-04-21 9:12 ` Stef Coene [this message]
2003-04-21 9:15 ` Stef Coene
2003-04-21 9:24 ` rio
2003-04-21 9:28 ` 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-105091660616965@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.