your device, may not have a queue length, try ip link set $DEV txqueuelen 1000 and see whether it limits correctly. On Fri, Feb 1, 2013 at 11:58 AM, 叶雨飞 <sunyucong@xxxxxxxxx> wrote: > your device, may not have a queue length, > > try > > ip link set $DEV txqueuelen 1000 > > and see whether it limits correctly. > > On Fri, Feb 1, 2013 at 11:20 AM, Neil Aggarwal <neil@xxxxxxxxxxxxxxxxxx> wrote: >> Hello: >> >> I have these commands in my firewall startup script: >> >> DEV=v1252 >> IP=a.b.c.d >> /sbin/tc qdisc del dev $DEV root >> /sbin/tc qdisc add dev $DEV root handle 1: htb default 30 >> /sbin/tc class add dev $DEV parent 1: classid 1:1 htb rate 10mbit >> /sbin/tc class add dev $DEV parent 1: classid 1:2 htb rate 10mbit >> /sbin/tc filter add dev $DEV protocol ip parent 1:0 prio 1 u32 match ip dst >> $IP flowid 1:1 >> /sbin/tc filter add dev $DEV protocol ip parent 1:0 prio 1 u32 match ip src >> $IP flowid 1:2 >> >> And tc qdisc list shows it has something for that dev: >> >> qdisc htb 1: dev v1252 root refcnt 2 r2q 10 default 30 direct_packets_stat 3 >> >> But, I am still seeing huge consumption of bandwidth from that server. >> Take a look at the attached graph. >> >> Any ideas why tc is not limiting the bandwidth? >> >> Thanks, >> Neil >> >> -- >> Neil Aggarwal, (972)834-1565, http://UnmeteredVPS.net/centos >> Virtual private server with CentOS 6 preinstalled >> Unmetered bandwidth = no overage charges -- To unsubscribe from this list: send the line "unsubscribe lartc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
