Peter Surda wrote:
at.matei schrieb:
Hi all,
hi
Can I use wrr with 8 classes each as leaf for each htb child?
Yes, but ESFQ may be better. I had stability problems when using more
than 1 WRR per interface, but it is possible that it's fixed now.
Furthermore, WRR is designed for large numbers so it is an overkill in
your situation.
Or, simply said: will each wrr classifier work on all seen ip
addresses or just the addresses from its htb parent.
Any seen IP, they are assigned dynamically. If there are too many, the
classes are "recycled" in a LIFO.
Ok, maybe I was not clear enough. What I'm interested in is the order of
passing throught filters. WRR has an built-in filter. HTB child classes
are fed by matching certain ip addresses (in my case htb chlid1 is for
x.x.x.0/29, htb child2 is for x.x.x.8/29 ) and so on. I want to attach
wrr1 as child to htb child 1 so the traffic get even divided between
clients x.x.x.0/29, wrr2 as child to htb child 2 and so on.
What I don't know is:
1/ tc filter match for is evaluated first
2/ if wrr1 is going to classify only hosts seen in x.x.x.0/29 or all
hosts x.x.x.0/24
Regards,
Alex
Thnaks for any comments,
NP.
Alex
Yours sincerely,
Peter
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
