All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] problem with IMQ
Date: Mon, 14 Apr 2003 15:47:20 +0000	[thread overview]
Message-ID: <marc-lartc-105033532612278@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105032830502606@msgid-missing>

On Monday 14 April 2003 16:01, hare ram wrote:
> Hi all
>
>
> iam working with Bridge with Linux RH 8.0
> when i making sample config in the document, iam getting following error
> could some one point me what is wrong
>
> i have patched the kernel and make also
> i have rebooted with new kernel
> but iam getting the folloing error
>
> [root@bridge root]# modprobe imq numdevs=1
> [root@bridge root]#  tc qdisc add dev imq0 handle 1: root htb default 1
> [root@bridge root]#  tc class add dev imq0 parent 1: classid 1:1 htb rate
> 1mbit
> [root@bridge root]#  tc qdisc add dev imq0 parent 1:1 handle 10: htb
> default 5
> [root@bridge root]#  tc class add dev imq0 parent 10: handle 10:1 htb rate
> 256kbit burst 30k prio 1
> Error: Qdisc "handle" is classless.
You mixed handle and classid in your commands.

> thanks for advance help
It's not such a good idea to add a htb qdisc to a htb class.  It will only 
create extra delays.

Stef

-- 

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

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

  parent reply	other threads:[~2003-04-14 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 13:51 [LARTC] problem with IMQ hare ram
2003-04-14 13:56 ` Hocking James A
2003-04-14 14:38 ` hare ram
2003-04-14 15:47 ` Stef Coene [this message]
2005-06-23 12:20 ` [LARTC] PROBLEM WITH IMQ s.az

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-105033532612278@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 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.