All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problem with HTB accurancy
Date: Fri, 28 Feb 2003 07:44:33 +0000	[thread overview]
Message-ID: <marc-lartc-104641834317180@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104638414219874@msgid-missing>


> >> My problem is that rrdtool graph shows :
> >>
> >>     ETH0 IN:        596.99Kbps
> >>     ETH0 OUT:    100.71Kbps
> >>
> >>     ETH1 IN:        74.44Kbps
> >>     ETH1 OUT:    150.13Kbps
> >>
> >> And the configuration has a ceil of 384Kbit
> >>
> >> What I'm doing wrong??
> >>
> >> I suppose that it could be with Squid Transparent Proxy, but in HTB
> >> I have a default classid 20,
> >> that is where must go any not specified traffic, how can I solve my
> >> problem?

> >> tc qdisc add dev eth0 root handle 1: htb default 20
> >> tc class add dev eth0 parent 1: classid 1:1 htb rate 100mbit ceil
> >> 384kbit burst 2k tc class add dev eth0 parent 1:1 classid 1:10 htb rate
> >> 56kbit ceil 64kbit burst 2k tc class add dev eth0 parent 1:1 classid
> >> 1:11 htb rate 56kbit ceil 64kbit burst 2k tc class add dev eth0 parent
> >> 1:1 classid 1:12 htb rate 56kbit ceil 64kbit burst 2k tc class add dev
> >> eth0 parent 1:1 classid 1:13 htb rate 56kbit ceil 64kbit burst 2k tc
> >> class add dev eth0 parent 1:1 classid 1:14 htb rate 56kbit ceil 64kbit
> >> burst 2k tc class add dev eth0 parent 1:1 classid 1:20 htb rate 100kbit
> >> ceil 128kbit burst 2k
My reply messed up the layout.  But 2kbit is too low for the burst.  Remove 
the burst parameter and htb will calculate the best burst for you.

> >> tc filter add dev eth0 parent 1: protocol ip prio 1 handle 1 fw classid
> >> 1:10 tc filter add dev eth0 parent 1: protocol ip prio 3 handle 3 fw
> >> classid 1:11 tc filter add dev eth0 parent 1: protocol ip prio 3 handle
> >> 5 fw classid 1:12 tc filter add dev eth0 parent 1: protocol ip prio 3
> >> handle 7 fw classid 1:13
You can give each filter the same prio.

If you go to http://www.docum.org/stef.coene/qos/monitor/ you can download my 
monitor_tc.pl script.  It will calculate the bandwidth but it will use the tc 
counters.  So you know exactly how much each class is sending.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-02-28  7:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 22:10 [LARTC] Problem with HTB accurancy Alexandra Alvarado
2003-02-28  7:44 ` Stef Coene [this message]
2003-03-06 16:34 ` Alexandra Alvarado
2003-03-07 17:15 ` Alexandra Alvarado
2003-03-08 20:34 ` Stef Coene

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=marc-lartc-104641834317180@msgid-missing \
    --to=stef.coene@docum.org \
    --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.