From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nataniel Klug <nata@cnett.com.br>
Date: Tue, 11 Apr 2006 15:58:34 +0000
Subject: Re: [LARTC] I dont want to shape a host
Message-Id: <443BD22A.50004@cnett.com.br>
List-Id: <lartc.vger.kernel.org>
References: <443ABE4F.7070806@cnett.com.br>
In-Reply-To: <443ABE4F.7070806@cnett.com.br>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: lartc@vger.kernel.org

Martin,

Thanks for the answer. I will study your topology and try to make this 
happens.

Att,

Nataniel Klug

Martin A. Brown escreveu:
> Nataniel,
>
> There are probably a handful of ways to solve this problem.  Two pop 
> to mind right away.
>
>  : I am still reading about my QoS rules and I need that one of my 
>  : servers (that is into my LAN but has an routing ip address) did 
>  : not get into the qos rules I have. So I want that all traffic 
>  : coming or going to that specifc host did not get shapped by any 
>  : traffic control and do not get even into a QoS class. How can I 
>  : do this?
>
> Option A:  specify "default 0" in your HTB qdisc declaration
> ==============================
> If you install the HTB qdisc with a "default 0" parameter, you are 
> telling HTB to dequeue unclassified packets as fast as the hardware 
> will accept the packets.  Here's an example:
>
>   tc qdisc add dev eth0 root handle 1:0 htb default 0
>
> Now, any unclassified packets will simply be dequeued as fast as 
> your hardware can do it.  If you are trying to remain the bottleneck 
> between you and the Internet, it is quite likely that this 
> configuration will defeat your goal.
>
>
> Option B:  make a deeper HTB tree
> ==============================
> Build the following:
>
>   class 1:0, rate = ceil = hardware maximum bitrate
>   class 2:0, rate = low, ceil = hardware maximum bitrate
>   class 3:0, rate = low, ceil = maximum for everybody else
>
>
>
>  root             +--- HTB 2:0 --- your "routing ip" (public 
>   |              /                 server?) goes here 
>   +-- HTB 1:0 --- 
>                  \
>                   +--- HTB 3:0
>                           |
>                           +--- HTB 3:1
>                           +--- HTB 3:2
>                           +--- HTB 3:3
>                           |        ...
>                           +--- HTB 3:N
>
> Now, you simply attach your filters to 1:0, like you did before, and 
> put all traffic for your "routing ip" into the 2:0 class.  If the 
> rate on class 2:0 stays "low", but its ceiling is the same as the 
> rate/ceil on 1:0, then you'll effectively get borrowing up to 
> maximum available throughput for HTB 2:0.
>
> Good luck,
>
> -Martin
>
>   
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc