Hi All, I have few queries in reference of HTB manuals on link http://luxik.cdi.cz/~devik/qos/htb/htbman.htm. 1> Is "default" is must while attaching queue discipline HTB to device? My observation for above question is, when I do following 4 command then I’ m able to reach to all hosts on eth1. But if I remove "default 12" from second command then I cannot reach to hosts on eth1, but I can reach to the host on other device (eth0, eth2). This occurs after I create extra class to serve as the root (i.e. creating class having parent 1:1, 4th command) tc qdisc del dev eth1 root tc qdisc add dev eth1 root handle 1: htb default 12 tc class add dev eth1 parent 1: classid 1:1 htb rate 100kbps ceil 100kbps burst 2k tc class add dev eth1 parent 1:1 classid 1:11 htb rate 10kbps ceil 100kbps burst 2k tc class add dev eth1 parent 1:1 classid 1:12 htb rate 60kbps ceil 100kbps burst 2k Ya, this reachability can be restored only after delition of root class, i.e. classid 1:1. I'm taking this as a feature but is it a bug? 2> Manual states that "... ... ... Now we can optionally attach queuing disciplines to the leaf classes... ... ... tc qdisc add dev eth0 parent 1:10 handle 20: pfifo limit 5... ... ...". If I not going to do that still I'm fine with my rule set, as written "optional". Then is there benefit or payoff against this leaf-class? 3> A Small but nice document about Cross device sharing on link http://luxik.cdi.cz/~devik/qos/htb/htbmeas1.htm. Can’t this limitation of slot be increased? 4> It would be nice if someone help me by providing statistics over number of queues and filter. What is maximum limit of these two for a PIII 700 with 256 MB RAM? How much maximum bandwidth can be shaped? Thanks in Advance. -- Sumit
