From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] [tcng] More complex example?
Date: Tue, 31 Dec 2002 10:25:46 +0000 [thread overview]
Message-ID: <marc-lartc-104133043328069@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104131492320647@msgid-missing>
On Tuesday 31 December 2002 07:07, Donald Gordon wrote:
> Hi
>
> I'm completely stuck with the tcng language - I assume there must be
> some way to arrange queues hierachically like
>
> eth1
>
> TBF
>
> PRIO
> / \
> class class
>
> but my attempt (below) produces a "inferno.tc:8: qdisc "tbf" has no
> classes near "prio"" when run through tcc.
Tbf is classless. So you can't add a prio qdisc to a tbf qdisc.
> dev eth1 {
> egress {
> tbf (rate 128kbps, burst 64kb, limit 64kb, mtu 1510B) {
> prio (bands 2) {
> $ssh_fast = SLB(cir 32kbps, cbs 3kB);
>
> class if ((tcp_sport == 22 || tcp_dport == 22) &&
> SLB_ok($ssh_fast));
> class if 1;
> }
> }
> }
> }
>
> Are there any examples of tcng scripts that do something slightly more
> complex than those in the tcng tarball?
You can take a cbq or htb qdisc and add the prio to 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-31 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 6:07 [LARTC] [tcng] More complex example? Donald Gordon
2002-12-31 10:25 ` Stef Coene [this message]
2003-01-01 1:18 ` Donald Gordon
2003-01-01 10:42 ` 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-104133043328069@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.