linux QOS流量管理实例二
作者 佚名技术
来源 Linux系统
浏览
发布时间 2012-05-17
t 1:0 prio 5 u32 match ip dst 192.168.1.200 flowid 1:100 #children - 256kbit tc class add dev eth1 parent 1:20 classid 1:200 htb rate 256Kbit ceil 1Mbit tc qdisc add dev eth1 parent 1:200 sfq quantum 1514b perturb 15 tc filter add dev eth1 protocol ip parent 1:0 prio 5 u32 match ip dst 192.168.1.55 flowid 1:200 #desktop - 256kbit tc class add dev eth1 parent 1:20 classid 1:300 htb rate 256Kbit ceil 1Mbit tc qdisc add dev eth1 parent 1:300 sfq quantum 1514b perturb 15 tc filter add dev eth1 protocol ip parent 1:0 prio 5 u32 match ip dst 192.168.1.11 flowid 1:300 #all other IPs from this class - 384kbit tc class add dev eth1 parent 1:20 classid 1:400 htb rate 256Kbit ceil 1Mbit tc qdisc add dev eth1 parent 1:400 sfq quantum 1514b perturb 15 tc filter add dev eth1 protocol ip parent 1:0 prio 5 u32 match ip dst 192.168.1.0/24 flowid 1:400 检验QOS配置 We need to verify the configuration we created by looking at the HTB classes. This is done with tc class show: root@router:~# tc class show dev eth1 class htb 1:10 root rate 100000Kbit ceil 100000Kbit burst 126575b cburst 126575b class htb 1:100 parent 1:20 leaf 8081: prio 0 rate 128000bit ceil 1000Kbit burst 1759b cburst 2849b class htb 1:20 parent 1:10 rate 1000Kbit ceil 1000Kbit burst 2849b cburst 2849b class htb 1:200 parent 1:20 leaf 8082: prio 0 rate 256000bit ceil 1000Kbit burst 1919b cburst 2849b class htb 1:300 parent 1:20 leaf 8083: prio 0 rate 256000bit ceil 1000Kbit burst 1919b cburst 2849b class htb 1:400 parent 1:20 leaf 8084: prio 0 rate 256000bit ceil 1000Kbit burst 1919b cburst 2849b So we see the root class 1:10, and the 1000Kbit (1Mbit) class 1:20 having the parent 1:10, and the other classes with their bandwidths having the parent 1:20. We need to see if packets match our classes. In case of zero traffic, we will verify that by pinging their IP address and seeing if they made a match for the corresponding class: root@router:~# ping -f -c 10 192.168.1.200 PING 192.168.1.200 (192.168.1.200) 56(84) bytes of data. --- 192.168.1.200 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 3ms rtt min/avg/max/mdev = 0.198/0.210/0.300/0.033 ms, ipg/ewma 0.394/0.230 ms root@router:~# tc -s class show dev eth1 | fgrep -A 4 1:100 class htb 1:100 parent 1:20 leaf 808d: prio 0 rate 128000bit ceil 1000Kbit burst 1759b cburst 2849b Sent 980 bytes 10 pkts (dropped 0, overlimits 0) lended: 10 borrowed: 0 giants: 0 tokens: 40962 ctokens: 12387 What we did was to send a flood ping with 10 packets to 192.168.1.200, and then check at the 1:100 class for the gaming device to see if those packets matched the class for the gaming device, and, as we expected, they did. |
凌众科技专业提供服务器租用、服务器托管、企业邮局、虚拟主机等服务,公司网站:http://www.lingzhong.cn 为了给广大客户了解更多的技术信息,本技术文章收集来源于网络,凌众科技尊重文章作者的版权,如果有涉及你的版权有必要删除你的文章,请和我们联系。以上信息与文章正文是不可分割的一部分,如果您要转载本文章,请保留以上信息,谢谢! |
你可能对下面的文章感兴趣
上一篇: Redhat5中discuz 7论坛的搭建下一篇: 玩转top
关于linux QOS流量管理实例二的所有评论