>> Does different rate / ceil for the root class make sense? >No. >Same for the classes attached to the root qdisc. They can not share >bandwidth. So your basi setup should be: >root htb qdisc > htb class with ceil = rate = link bandwidth > other classes So following script is reccomended? tc qdisc add dev eth0 root handle 1: htb default 11 r2q 10 # Class corresponding external interface throughput (for 115kbit ADSL) tc class add dev eth0 parent 1: classid 1:1 htb rate 115kbit ceil 115kbit # Classes for PC-s tc class add dev eth0 parent 1:1 classid 1:11 htb rate 55kbit ceil 115kbit prio 2 tc class add dev eth0 parent 1:1 classid 1:12 htb rate 48kbit ceil 115kbit prio 3 tc class add dev eth0 parent 1:1 classid 1:13 htb rate 12kbit ceil 115kbit prio 4 #End if script What can I do if the same interface (eth0) is used for other purposes (internal traffic generated from local servers)? If HTB class has the highest ceil set to 115kbit, how can I define other classes for example for internal traffic? Zviad _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
