Original Message:
-----------------
From: Stef Coene stef=2Ecoene@docum=2Eorg
On Saturday 19 April 2003 17:19, rio@martin=2Emu wrote:
>> On Saturday 19 April 2003 12:10, GoMi wrote:
>> Sadly my users often download with 3 - 5 DAP=2E So when i sniff their
>> connection, the results of tcp connection arrount 30 tcp connection to
>> remote host port 80=2E
>So it's just parallel tcp sessions to the same hosts=2E But if you put t=
he=20
>traffic from each host in 1 class, each class (and so each host) has the
>same right for bandwidth=2E =20
I give you real situation in my network:
eth0[PUBLIC=2EIP]
LINUX - BW - Manager
eth1[192=2E168=2E1=2E10]
|
|
4 hosts: 192=2E168=2E1=2E1 - 192=2E168=2E1=2E4
My total bandwidth is only 128Kbit
All NICs are Realtek 10Mbit
So the solution as you offered is to put each class 128Kbit/4 =3D 32Kbit?
If that so, then it would be good if i use CBQ qdisc, not HTB=2E I want to=
use HTB because HTB burstable=2E
Please suggest=2E=2E
Regards,
Rio Martin=2E
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web=2Ecom/ =2E
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 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.
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
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