All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc + zebra/quagga
Date: Mon, 28 Mar 2005 22:05:04 +0000	[thread overview]
Message-ID: <42487F90.8090207@dsl.pipex.com> (raw)
In-Reply-To: <200503231911.37430.lorin@si-bemol.ro>

Lorin wrote:

> 
>  It would be quite some work to setup a configuration, there are a lot of 
> hosts that need to be limited.

I really meant can you recreate it with a simple test case without lots 
of rules.

>  Here is what I have:
> 
> #---class root - RATE/CEIL\x100Mbit
> /sbin/tc class add dev eth0 parent 1: classid 1:0010 htb rate 100Mbit
> /sbin/tc qdisc add dev eth0 root handle 1 htb default 3000

This is the wrong way round - if you didn't get an error prehaps there 
was already a queue on from a previous test - that could confuse things.

>  
> #---class bgp - RATE/CEIL\x128Kbit
> /sbin/tc class add dev eth0 parent 1:0010 classid 1:0050 htb rate 128Kbit ceil 
> 128Kbit prio 0
> /sbin/tc qdisc add dev eth0 parent 1:0050 handle 0050 sfq perturb 10

I am not sure if it makes a difference but normally the handle would be 
0050: maybe it is clashing with the parent classid without the :


>  If I set the leaf qdisc to 'none' traffice gets classified well; if I use a 
> qdisc in a child class all traffic goes to default.
>  After few tests I managed to isolate the problem (kinndof) - if I use just 
> one class, best-effort for example, and put all filters/qdisc in this one 
> everything works fine. But I really need to separate big clients (premium) 
> from small ones (best-effort) and to shape management/bgp traffic separately 
> from those 2. atm the only separations is made after prio value: bgp 0, 
> management 1, premium 2, best-effort 3 and default 7.

It should be doable - I may have missed something else. I assume you are 
testing with

tc -s qdisc ls dev eth0
tc -s class ls dev eth0
tc -s filter ls dev eth0

not nice with lots of rules - but worth it to check the counters.

> 
> Thanks for the help!
> 
> p.s.
>  I'm working on a romanian translation for LARTC. I have about 1/4 of it till 
> now. If there are any romanians on this list willing to help it would a very 
> nice thing to do for the community. Also translating this great howto it's a 
> study itself so you can get also some solid knowledge besides the Glory:) 

I think the list had died again - so make sure you cc me if you reply.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-03-28 22:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23 17:11 [LARTC] tc + zebra/quagga Lorin
2005-03-27 11:50 ` Andy Furniss
2005-03-28  8:07 ` Lorin
2005-03-28 22:05 ` Andy Furniss [this message]
2005-03-29 15:29 ` Lorin
2005-04-04 11:17 ` Lorin

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=42487F90.8090207@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --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.