Skip to contentSkip to conversation

probably solved... why all goes to default!!

LARTC raptor 3 participants 3 messages Nov 19, 2003

lore
Share & tools
lore

raptor

author
#0 lore raw

I seem to solved the problem !!
just on top of my head... I had the following config (by memory) :

root qdisc htb

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

and with u32-fitlter attached to root I directed the traffic to class Y,Z etc.... Now i made it like this :

root qdisc htb

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

u see no qdisc....and it works.. do u have explanation ?! ... take into account that class X is htb :")

Quoted 2 lines

yep my test kernel is 2.4.22-ck, but this also happens on other machine with 2.4.20 kernel !! i'm with gentoo.. So it has to be something into the kernel.. that is in both of them..!?

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#1 lore raw
Quoted 25 lines · raptor

I seem to solved the problem !!
just on top of my head... I had the following config (by memory) :

root qdisc htb

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

and with u32-fitlter attached to root I directed the traffic to class Y,Z etc.... Now i made it like this :

root qdisc htb

  |---class X htb
  |
  |             |---class Y => qdicsY
  |             |---class Z => qdicsZ
  |
  |---class A
Quoted 2 lines

u see no qdisc....and it works.. do u have explanation ?! ... take into account that class X is htb :")

A filter only works within 1 qdisc. You can get your first setup working if you add 2 filters, one for the root qdisc and one for the qdisc X.

Stef

Signature · 8 lines
[email protected]
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.openprojects.net

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#2 lore raw
In reply to raptor
Quoted 5 lines
 |---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 / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/