-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello again Raku,
: you mean we can define "nested qdisc" but algorithm in nested
: qdisc must same as parent class???? i'm not clear it and Is we
: can define nested qdisc with algorithm different from parent
: class?????
Next try at explaining the concept:
- qdiscs can be attached to egress (default), ingress and any
class
- classes may only be defined "underneath" (as children of)
existing classful qdiscs (CBQ, HTB, PRIO, HFSC)
- a classful qdisc may only have children classes of the same type
(e.g., HTB qdisc can only have HTB classes; HFSC qdisc can only
have HFSC classes)
- classless qdiscs are leaf branches on the tree
Be careful to distinguish classes from qdiscs.
: tc qdisc add dev eth0 root handle 1: htb
: //this left node hierachy for manage general package
: tc class add dev eth0 parent 1: classid 1:1 htb rate 100kbps ceil 100kbps
: //this right node hierachy for manage real time package
: tc class add dev eth0 parent 1: classid 1:2 htb rate 100kbps ceil 100kbps
: // from your adivse at step 4, attach brand-new after define class
: but Is it true??? because algorithm new qdisc are different from
: class algorithm that qdisc attach it.
: tc qdisc add dev eth0 parent 1:2 classid 10:11 hfsc rate 100kbps
: tc class add dev eth0 parent 10:11 classid 1:111 hfsc rate 100kbps ceil
: 100kbps
: tc class add dev eth0 parent 10:11 classid 1:112 hfsc rate 100kbps ceil
: 100kbps
Structurally speaking, there's nothing wrong with your hierarchy.
When you try it out, however, you'll discover that you are not using
the correct parameters for the hfsc qdisc and class specifications.
: and Can somebody advise me about HOW TO do later in this topic. i
: want to have got traffic shaper and my solotion is ... i want to
: manage different traffic package (general package use and real
: time package) so now i think about have got a problem with tc
: command, ... i think it can't setting to manage different package
: with different algorithm HTB and HFSC Do you have any idea about
: how to setting tc command example???? thank you
Raku, I don't know whether HTB or HFSC would be better for your
application, but I can tell you that HTB is better-understood by a
larger number of people. In the grand scheme of things, HFSC has
seen far less use. It's an excellent concept, and if you'd like to
know more about the concepts behind the queuing discipline, I'd
suggest the HFSC article by Klaus Rechert and Patrick McHardy [0].
I think a simple hierarchy almost exactly like the one detailed in
their article is probably what you want. It sounds like you have
"realtime" traffic (e.g., VoIP) and bulk traffic.
So, read their documentation, and try to configure your traffic
control structures as they suggest. Once you have configured the
traffic control structures, then add the filters to separate traffic
into the appropriate classes, e.g.:
FILTR="tc filter add dev $INTERFACE"
# -- structure is built, now select some packets
#
$FILTR parent 1:0 protocol all prio 1 \
u32 match ip src 192.168.7.0/24 flowid 1:10
# -- example for grabbing anything at all
#
$FILTR parent 1:0 protocol all prio 1 \
u32 match u32 0x0 0x0 at 0 classid 1:11
# -- example for identifying all UDP traffic
#
$FILTR parent 1:0 protocol all prio 1 \
u32 match u8 0x11 0xff at 9 classid 1:12
These are just example filters (and probably not great examples at
that). You should write your filters to select the traffic you want
to place into each class.
Finally, let me recommend that you keep your class structure as
simple as possible.
- -Martin
[0] http://linux-ip.net/tc/hfsc.en/
- --
Martin A. Brown
http://linux-ip.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: pgf-0.71 (http://linux-ip.net/sw/pine-gpg-filter/)
iD8DBQFEt7zjHEoZD1iZ+YcRAqBEAKCnuuyDblK9pKvG4Og12HJovGt3HQCcD3LD
u0rdSUkjmgmBJtJ/gpIfc0M=
=V1fF
-----END PGP SIGNATURE-----_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
