From: Emmanuel Guiton <emmanuel@netlab.hut.fi>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] unknown qdisc 'htb' ???
Date: Tue, 04 Feb 2003 14:29:17 +0000 [thread overview]
Message-ID: <marc-lartc-104436904202737@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101177192616207@msgid-missing>
Hello,
Could you tell me how did you solve your problem?
I have exactly the same problem but with this configuration:
- linux 2.4.20 kernel, HTB option checked
- iproute2-2.4.7-now-ss010824.tar.gz installed, which is the latest version I found at ftp://ftp.sunet.se/pub/Linux/ip-routing/, except for "try" or "do not use" versions.
I guess I do not need patching iproute2 and I'm not using an old version of tc either.
Or am I wrong somewhere?
Br,
Emmanuel
>Hello,
>
>I'd like to try out HTB for traffic shaping.
>
>I have a test machine with Redhat 7.2 (kernel 2.4.10), I've downloaded
>kernel 2.4.17, applied the patch from http://luxik.cdi.cz/~devik/qos/htb/, <http://luxik.cdi.cz/%7Edevik/qos/htb/,>
>recompiled the kernel (checked the option to use HTB in make menuconfig),
>and rebooted with the new kernel.
>
>When I try to add some rules with HTB (f.i. tc qdisc add dev eth0 root
>handle 1: htb default 1:1 ), I got the following error message:
>Unknown qdisc "htb", hence option "default" is unparsable
>
>Obviously, this is not what I want :-)
>
>What is going wrong here?
>
>Regards,
>Patrick
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-02-04 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 7:44 [LARTC] unknown qdisc 'htb' ??? Patrick Van Acker
2002-01-23 8:09 ` Stef Coene
2002-01-23 14:24 ` Patrick McHardy
2003-02-04 14:29 ` Emmanuel Guiton [this message]
2003-02-04 14:43 ` David DeLauro
2003-02-04 15:03 ` Emmanuel Guiton
2003-02-04 15:14 ` Stef Coene
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-104436904202737@msgid-missing \
--to=emmanuel@netlab.hut.fi \
--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.