Your setup doesn't make much sense. Two htbs can be done but there is no benefit. tc qdisc add dev eth1 parent 100:2 handle 102:1 is wrong because each qdisc handle takes form X:0 not X:1 ... devik On Wed, 6 Mar 2002, eth wrote: > Until now I've been using HTB instead of CBQ and it worked quite > good. I try now to prio ICMP and SSHwith the following: > > tc_htb qdisc add dev eth1 root handle 1: htb default 10 > > # total > #78Kbytes > tc class add dev eth1 parent 1: classid 1:1 htb rate 76kbps ceil 78kbps > burst 2k > > #50Kbytes > tc class add dev eth1 parent 1:1 classid 1:10 htb rate 48kbps ceil > 76kbps burst 2k > #PRIO as qdisk for this slice > tc qdisc add dev eth1 parent 1:10 handle 100: prio > #I try to avoid a situation where a "massive" ping would disrupt > everything else > tc qdisc add dev eth1 parent 100:1 handle 101 tbf rate 8kbps > latency 1500ms burst 1540 > #The second band (probably HTTP) shouldn't eat everything from FTP > which should be tc filtered in band 3... > tc qdisc add dev eth1 parent 100:2 handle 102:1 htb default 100221 > > tc class add dev eth1 parent 102:1 classid 1002:1 htb rate 40kbps > ceil 76kbps burst 2k > > ... and the last line gives me an error: RTNETLINK answers: Invalid > argument. Why? > > _______________________________________________ > LARTC mailing list / LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ > >
