Displaying 2 results from an estimated 2 matches for "3100kbit".
Did you mean:
100kbit
2007 Sep 19
1
major packet loss with htb
...evel 0
Sent 328942394630 bytes 480708749 pkt (dropped 1725703, overlimits 0
requeues 0)
rate 17344Kbit 3494pps backlog 0b 58p requeues 0
lended: 290657995 borrowed: 190050689 giants: 0
tokens: -2409 ctokens: -1914
class htb 1:30 parent 1:1 leaf 30: prio 5 quantum 37500 rate 3000Kbit
ceil 3100Kbit burst 1974b/8 mpu 0b overhead 0b cburst 1986b/8 mpu 0b
overhead 0b level 0
Sent 66686833287 bytes 127212829 pkt (dropped 3728008, overlimits 0
requeues 0)
rate 3099Kbit 792pps backlog 0b 126p requeues 0
lended: 121903109 borrowed: 5309594 giants: 0
tokens: -6323 ctokens: -6993
1:10 is i...
2013 Nov 14
1
Possible bug: TC with HFSC fails to load if umax is not provided
...ev eth1 parent 1:1 classid 1:110 hfsc sc
umax b dmax 150ms rate 1575kbit ul rate 3150kbit" Failed
After some investigation of /var/lib/shorewall/firewall I found the above
line to be:
run_tc class add dev eth1 parent 1:1 classid 1:110 hfsc sc umax
${eth1_mtu}b dmax 150ms rate 1550kbit ul rate 3100kbit
But eth1_mtu was not defined anywhere! Hence it was getting the parmeter
"umax b" where it should apparently say "umax 1500b".
In the file generated by older version - /var/lib/shorewall/restore, just a
few lines above run_tc line was this one:
eth1_mtu=$(get_device_mtu eth1)...