From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] kernel 2.4.18-17.7.x from redhat
Date: Tue, 22 Oct 2002 14:39:24 +0000 [thread overview]
Message-ID: <marc-lartc-103529764528920@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103515453230788@msgid-missing>
On Tuesday 22 October 2002 12:02, Ciprian Niculescu wrote:
> Stef Coene wrote:
> >>>>the tc from redhat knows about htb???
> >>>
> >>>Don't know, but if they have support in the kernel for htb, tc will have
> >>>it too.
> >>
> >>tc qdisc add dev eth0 handle 1: root htb default 6
> >>Unknown qdisc "htb", hence option "default" is unparsable
> >>
> >>and it's compiled in kernel, not module
> >
> > You miss support for htb in the tc command. There is a binary on the
> > homepage of htb, or you can download the iproute2 src + the patch from
> > the homepage of htb and create your own binary.
>
> yes, i know, i don't have intentions on using shapping on that router,
> was just an observation that redhat put the htb in kernel, but, didn't
> put an update to iproute2 allready patched. They did a half work :((
Conclusion : don't use RedHat :)
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/
next prev parent reply other threads:[~2002-10-22 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 22:52 [LARTC] kernel 2.4.18-17.7.x from redhat Ciprian Niculescu
2002-10-21 13:16 ` Stef Coene
2002-10-21 20:59 ` Ciprian Niculescu
2002-10-22 5:59 ` Stef Coene
2002-10-22 10:02 ` Ciprian Niculescu
2002-10-22 14:39 ` Stef Coene [this message]
2002-10-22 19:16 ` Kenneth Porter
2002-11-24 22:19 ` Kenneth Porter
2003-01-16 21:23 ` Kenneth Porter
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-103529764528920@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