From: Werner Almesberger <wa@almesberger.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tcng questions ?
Date: Sun, 14 Jul 2002 00:39:23 +0000 [thread overview]
Message-ID: <marc-lartc-102660699924980@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102658719214618@msgid-missing>
raptor@unacs.bg wrote:
> - Does tcng support HTB ? syntax ?
Not yet. Someone's working on implementing support for it, so I
hope to have it in the not too distant future.
> - what is the difference between "if" and "on" ?
"on" gives direct access to the filters of Linux traffic control,
while "if" provides a more abstract language.
I'm reading the docs but can get it right !
> "if" uses bool expressions and "on" is using only "u32", correct ?!
Half of it ;-) "on" supports all filters except u32. "if" uses u32
to do its work.
> what more?
Eventually, I plan to phase out "on". If you look at the documentation,
the elements in "The tcng language" are here to stay, while the ones in
"Under the hood" may change, and the ones in "Historical constructs"
should eventually disappear.
> - how can I tell tcng to use iptables for classifying and what is the
> syntax for it ?
You'll have to use the "fw" classifier. tcng doesn't touch iptables
directly, so you'd have to set up that classification separately.
For static classification, "if" is probably more convenient to use
than a mixture of iptables and tcng.
> if I want all packets that are not classified to be dropped what i have to do, is this correct :
>
> dev eth0 {
> class (1) if ....;
> class (2) if ....;
> class (3) drop if 1;
> }
It's either
dev eth0 {
name_of_qdisc { /* except if that qdisc is prio and your kernel isn't
very very recent */
class (1) if ...;
class (2) if ...;
drop if 1;
}
}
Or, better
dev eth0 {
egress {
class (<$c1>) if ...;
class (<$c2>) if ...;
drop if 1;
name_of_qdisc {
$c1 = class (1);
$c2 = class (1);
}
}
}
The second form gives you a better separation of classification
and queuing, and you also don't have to worry about drop not
working (in the case of "prio"). As a disadvantage, the second
form adds an indirection through "dsmark" and "tcindex".
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://icapeople.epfl.ch/almesber/_____________________________________/
_______________________________________________
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-07-14 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 19:05 [LARTC] tcng questions ? raptor
2002-07-14 0:39 ` Werner Almesberger [this message]
2002-07-14 11:10 ` Martin Devera
2002-07-14 19:01 ` raptor
2002-07-15 8:22 ` devik
2002-07-15 13:57 ` Tobias Geiger
2002-07-16 22:36 ` Jacob Teplitsky
2002-07-19 17:58 ` raptor
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-102660699924980@msgid-missing \
--to=wa@almesberger.net \
--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.