search for: defmap

...questions about "tc" parameters: What is "weight" for? We''ve seen that leaving it out of our script causes error/warnings like: CQB: class 00010012 had bad quantum==0, repaired. Which values should it have and why? When should one use the "split" and "defmap" parameters? I guess they can be used to specify the best effort class, but what value should split have and how do you read/understand the hex value of defmap? A last note to the HOWTO maintainers: thanks.

...u 64 $TC class add dev $DEVICE parent 1:0 classid :1 est 1sec 8sec cbq \ bandwidth $RATE rate $RATE allot 1514 maxburst 50 avpkt 1000 $TC class add dev $DEVICE parent 1:1 classid :2 est 1sec 8sec cbq \ bandwidth $RATE rate $BE_RATE allot 1514 weight 500Kbit \ prio 6 maxburst 50 avpkt 1000 split 1:0 defmap ffff borrow $TC class add dev $DEVICE parent 1:1 classid :3 est 2sec 16sec cbq \ bandwidth $RATE rate `echo $2/2|bc`Mbit allot 1514 weight 100Kbit \ prio 2 maxburst 100 avpkt 1000 split 1:0 defmap c0 $TC class add dev $DEVICE parent 1:1 classid :4 est 1sec 8sec cbq \ bandwidth $RATE rate 100Kbit...

...h on equal footing (after the appropriate delay has been applied, of course). So, instead of a prio multiband qdisc, I''d be interested in a round-robin one. Can I accomplish this with CBQ ? What would the tc commands have to look like -- I''m getting slightly confused by the split/defmap syntax, and by trying to figure out when it''s a clas vs a qdisc I''m supposed to be dealing with... :( I guess I should be looking at using the WRR qdisc, but I''d like to try everything else I can before falling through to adding an out-of-tree kernel module and patching...

...ow, I understand it all for rate control on users - what I can''t figure out is how we can shape / prioritize by protocol (ie, treat ssh / telnet higher than www which is higher than ftp, etc). I suppose we could use the "split" command (9.5.4.5. Other CBQ parameters: split & defmap) but we would still require a separate rule for each user. What does that mean -> well, we have one rule for each interface (minimum 2) - one rule for each customer for each interface - AND one rule for each traffic filter for each customer for each interface!!! Obviously with several hundre...