Re: Re: [LARTC]probably solved... why all goes to default!!

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>  |---class X htb => qdisc X
>  |                     |---class Y ==> qdicsY  
>  |                     |---class Z ==> qdicsZ  
>  |---class A

Just a guess, but:
In this configuration the root qdisc (to which your filters are attached)
doesn't know anything about classes Y and Z; it only "sees" _class_ X and A.
So it cannot direct the traffic to Y or Z.
Also this way you increase the delay on the link:

"HTB as child of another HTB is NOT the same as class under another
class within the same HTB. It is because when class in HTB can send it
will send as soon as hardware equipment can. So that delay of underlimit
class is limited only by equipment and not by ancestors.
In HTB under HTB case the outer HTB simulates new hardware equipment
with all consequences (larger delay)"
(Taken from the HTB User Guide -
http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm)

~ tv ~


_______________________________________________
LARTC mailing list / LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux