From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multiple classes
Date: Tue, 03 Dec 2002 10:29:00 +0000 [thread overview]
Message-ID: <marc-lartc-103893701621052@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103889506715109@msgid-missing>
On Tuesday 03 December 2002 06:49, Homer Parker wrote:
> I'm trying to implement something similar the the diagram in section
> 9.5.2.1 in the LARTC HOWTO, but must have missed something somewhere :(
> I'm trying to hack up wondershaper, as it looked like a good place to
> start.. Here's where I currently at, but I've tried alot of different
> things, all failing, some worse than others. The end result is to throttle
> back 126 IP's individually. I've read so much over the last few days, I've
> almost confused myself, and probably have ;) Thanks for any and all help!
>
> tc qdisc add dev $DEV0 root handle 1: htb default 20
>
> tc class add dev $DEV0 parent 1: classid 1:1 htb rate 128kbit \
> burst 6k
>
> tc class add dev $DEV0 parent 1:1 classid 2: htb rate 128kbit \
> burst 6k
All class attached to the same qdisc have the same major number. Numbering of
classes and qdiscs : <major nuber>:<minor numer>.
2: is a valid name for a qdisc, but not for a class.
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-12-03 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 5:49 [LARTC] Multiple classes Homer Parker
2002-12-03 10:29 ` Stef Coene [this message]
2002-12-03 17:39 ` Homer Parker
2002-12-03 21:03 ` Stef Coene
2002-12-04 10:08 ` Homer Parker
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-103893701621052@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