Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: anderson@skyweb.co.ke
To: lartc@vger.kernel.org
Subject: [LARTC] Ceil Rate
Date: Fri, 30 Sep 2005 16:13:39 +0000	[thread overview]
Message-ID: <20050930161339.GA25083@localhost.home.com> (raw)

Hi all,

I just recently began using HTB to try and manage bandwidth for my network.
This is the script I'm using:

/sbin/iptables -t mangle -A FORWARD -o eth1 -s ! 192.168.244.2 -j MARK --set-mark 53

tc qdisc add dev eth1 root handle 1: htb default 20

tc class add dev eth1 parent 1: classid 1:1 htb rate 100mbit burst 131072k quantum 59000

tc class add dev eth1 parent 1:1 classid 1:10 htb rate 64kbit quantum 1501
tc class add dev eth1 parent 1:1 classid 1:20 htb rate 1kbit ceil 100mbit burst 131072k quantum 1600

tc qdisc add dev eth1 parent 1:10 handle 10: sfq perturb 10
tc qdisc add dev eth1 parent 1:20 handle 20: sfq perturb 10

tc filter add dev eth1 protocol ip parent 1:0 prio 1 handle 53 fw flowid 1:10

The problem is I often find the rate exceeding the ceil which is 64kbit for 1:10 when I ran this
command:
	
		tc -s show class dev eth1

I'm also using a script that captures the output of the above command and
feeds it to rrdtool to plot a graph of the usage and it also shows that the
bandwidth being utilised exceeds 64kbit.

How can ensure that this doesn't happen? Where did I go wrong with my
config?

Any help would be appreciated.


Thanks.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2005-09-30 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 16:13 anderson [this message]
2005-09-30 22:29 ` [LARTC] Ceil Rate Jody Shumaker
2005-10-04  7:23 ` anderson
2005-10-05  0:46 ` Jody Shumaker

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=20050930161339.GA25083@localhost.home.com \
    --to=anderson@skyweb.co.ke \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox