RE: Tc does not seem to be limiting bandwidth

["Neil Aggarwal" <neil@JAMMConsulting.com>]

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

Andy:

> If that is the case, you'll need an ingress

You were right, I needed to add an ingress filter to limit the upload
speed of the VPS.  So, now here are my rules:

IP=a.b.c.d
DEV=v1208
/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 5mbit
/sbin/tc class add dev $DEV parent 1: classid 1:2 htb rate 5mbit
/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
/sbin/tc qdisc del dev $DEV ingress
/sbin/tc qdisc add dev $DEV ingress handle ffff:
/sbin/tc filter add dev $DEV parent ffff: protocol ip prio 50 u32 match ip src 0.0.0.0/0 police rate 5mbit burst 500k drop flowid :1

I am attaching a graph that shows the bandwidth during two large file transfers.

The first part of the graph is when I was doing a large download.  
It sits exactly at 5mbit/sec which is what I want it to do.

Next, I stopped the download and started an upload.  That is sitting at 
about 60kbit/sec and not going any higher.

Any ideas why the ingress rules are limiting the bandwidth so much?

Thank you,
  Neil

--
Neil Aggarwal, (972)834-1565, http://UnmeteredVPS.net/centos
Virtual private server with CentOS 6 preinstalled
Unmetered bandwidth = no overage charges

[-- Attachment #2: bandwidth.png --]
[-- Type: image/png, Size: 23813 bytes --]