All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Neil Aggarwal" <neil@JAMMConsulting.com>
To: lartc@vger.kernel.org
Subject: Tc does not seem to be limiting bandwidth
Date: Fri, 01 Feb 2013 19:20:12 +0000	[thread overview]
Message-ID: <000101ce00b1$2856c670$79045350$@JAMMConsulting.com> (raw)

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

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

[-- Attachment #2: graph.png --]
[-- Type: image/png, Size: 38173 bytes --]

             reply	other threads:[~2013-02-01 19:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 19:20 Neil Aggarwal [this message]
2013-02-01 19:58 ` Tc does not seem to be limiting bandwidth 叶雨飞
2013-02-01 19:59 ` Outofwall.com
2013-02-03 16:53 ` Neil Aggarwal
2013-02-03 21:35 ` Andrew Beverley
2013-02-03 23:34 ` Neil Aggarwal
2013-02-03 23:55 ` Neil Aggarwal
2013-02-04  0:35 ` 叶雨飞
2013-02-04  1:17 ` Neil Aggarwal
2013-02-04 22:57 ` Andrew Beverley
2013-02-04 22:59 ` Andrew Beverley
2013-02-05  0:11 ` Neil Aggarwal
2013-02-05  7:33 ` Andrew Beverley
2013-02-05  7:35 ` Andrew Beverley
2013-02-09  3:27 ` Neil Aggarwal
2013-02-10 11:03 ` Andrew Beverley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000101ce00b1$2856c670$79045350$@JAMMConsulting.com' \
    --to=neil@jammconsulting.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.