From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] cbq bounded problem
Date: Thu, 05 Jun 2003 07:41:36 +0000 [thread overview]
Message-ID: <marc-lartc-105479899102624@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105478781427244@msgid-missing>
On Thursday 05 June 2003 06:35, Zealous wrote:
> Dear all,
>
> I have 1 mbps line to internet.
>
> Our linux server is connected to router of 1mb
>
> Linux server gets 1mb bandwidth.
>
> I have done SOURCE MASQUERADING on linux.
>
> I have attached a cbq bandwidth script. I want to allow the traffic to
> restrict to 200Kbps. it should not exceed beyond 200.
>
> I have made a configuration and i kept on the server but the traffic goes
> beyond 200 .....it even goes to 350 and 400. how can i restrict the traffic
> on 200. ????
> plz check the attached script .
> plz open in word.
> any help is great for me.
Some tips :
- Adding the sfq qdisc to class 10:200 is useless. It's removed as soon as
you add a subclass.
- Are you sure your packes are queued in the class you want? Check it out
with tc -s -d class show dev eth4.
- prio 100 is too much. The maximum is 7.
- avpkt 800 should reflect your average packet size. Are you sure it's only
800 bytes?
- Is your NIC configured at 10Mbit? (bandwidth parameter)
Take weight = rate / 10.
- Use htb and visit www.docum.org :)
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/
next prev parent reply other threads:[~2003-06-05 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 4:47 [LARTC] cbq bounded problem Zealous
2003-06-05 7:41 ` Stef Coene [this message]
2003-06-06 3:41 ` [LARTC] CBQ " Zealous
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-105479899102624@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.