Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: [LARTC]probably solved... why all goes to default!!
Date: Wed, 19 Nov 2003 18:30:49 +0000	[thread overview]
Message-ID: <marc-lartc-106926827828414@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106924268828268@msgid-missing>

On Wednesday 19 November 2003 12:51, raptor wrote:
> I seem to solved the problem !!
> just on top of my head... I had the following config (by memory) :
>
>
> root qdisc htb
>
>   |---class X htb => qdisc X
>   |
>   |                                     |---class Y => qdicsY
>   |                                     |---class Z => qdicsZ
>   |
>   |---class A
>
> and with u32-fitlter attached to root I directed the traffic to  class Y,Z
> etc.... Now i made it like this :
>
> root qdisc htb
>
>   |---class X htb
>   |
>   |             |---class Y => qdicsY
>   |             |---class Z => qdicsZ
>   |
>   |---class A
>
> u see no qdisc....and it works.. do u have explanation ?! ... take into
> account that class X is htb :")
A filter only works within 1 qdisc.  You can get your first setup working if 
you add 2 filters, one for the root qdisc and one for the qdisc X.

Stef

-- 
stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.openprojects.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-11-19 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 11:51 [LARTC] Re: [LARTC]probably solved... why all goes to default!! raptor
2003-11-19 18:30 ` Stef Coene [this message]
2003-11-19 19:15 ` trepo

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-106926827828414@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox