All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stafke@iname.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] traffic always bounded ??
Date: Fri, 30 Mar 2001 05:45:16 +0000	[thread overview]
Message-ID: <marc-lartc-98593170812963@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98588418022015@msgid-missing>

> Philippe Amelant wrote:
> 
> Hi,
> 
> I have installed cbq on a bridge.
> I use cbq-init 0.6.1
> It work well, but i still have a problem with it.
> 
> I have something like that
> 
> root -> class 1 (not isolated, not bounded)->  subclass 1 (not
> isolated, not bounded)
>                                                            -> subclass
> 2 (not isolated, not bounded)
>                                                            -> subclass
> 3 (not isolated, not bounded)
>       -> class 2 (not isolated, not bounded)
> 
> it seems to work well, but when I try to make some test,
> i can see that one class cannot borrow bandwidth to other class !
Did you attached a qdisc to subclass1 ? ?

> are they any thing special to do  to get it working ?
> 
> by the way if you have some link for other doc... :)

More info : http://users.belgacom.net/staf/   I'm working on the site,
but there is som usefull information.  Look at my scripts an try to
figure out how they work.

If you wanna help, plz let me know :-)

Staf

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

  reply	other threads:[~2001-03-30  5:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-29 16:41 [LARTC] traffic always bounded ?? Philippe Amelant
2001-03-30  5:45 ` Stef Coene [this message]
2001-03-30 12:46 ` Philippe Amelant

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-98593170812963@msgid-missing \
    --to=stafke@iname.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.