Displaying 2 results from an estimated 2 matches for "768000bit".
Did you mean:
768000bits
2010 Apr 22
1
PRIO qdisc + iptables TOS target
...child PRIO
tc class add dev imq0 parent 1:1 classid 1:99 htb rate 96kbit ceil
600kbit prio 0
tc qdisc add dev imq0 parent 1:99 prio
tc filter add dev imq0 parent 1: protocol ip prio 7 u32 match ip dst
192.168.1.99 flowid 1:99
the result is:
# tc - s class ls dev imq0
class htb 1:1 root rate 768000bit ceil 768000bit burst 1599b cburst 1599b
Sent 2451 bytes 22 pkt (dropped 0, overlimits 0 requeues 0)
rate 1016bit 1pps backlog 0b 0p requeues 0
lended: 0 borrowed: 0 giants: 0
tokens: 250000 ctokens: 250000
class htb 1:129 parent 1:1 leaf 816c: prio 0 rate 96000bit ceil
600000bit burst 1599b cb...
2006 Feb 20
6
HTB, strange capacity distribution
Hello,
after spending several hours reading archives, I decided to write new
post.
I successfully set up packet classification, made some basic HTB
setup, made some simple graphical representation from HTB statistics
data...
BUT, I cannot figure out how to refine HTB to get this behaviour:
I need that class "p2p" should be the last one to get some link
capacity.
If I set both RATE