From: "lartc@manchotnetworks.net" <lartc@manchotnetworks.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] TC-ng questions/problems
Date: Thu, 05 Aug 2004 09:59:20 +0000 [thread overview]
Message-ID: <1091699959.13878.4.camel@drs0> (raw)
In-Reply-To: <A3D1526C98B7C1409A687E0943EAC41001EA61@obelix.askesis.nl>
Hi Joost,
OK -- on the units of measure -- you may to double check that your
upstream provider is 2.000.000 bits/s and not 2 * 1024^1024.
I think that your r2q is probably off -- please see:
http://www.docum.org/stef.coene/qos/faq/cache/31.html
Check your system log as well -- you may see an indication of the
problem. You can try
#define MYR2Q 20
and then in your htb declaration try
htb ( r2q MYR2Q )
Also consider specifying a burst of 6kB and try someother values.
Cheers
Charles
On Thu, 2004-08-05 at 10:26, Joost Kraaijeveld wrote:
> Hi Chalres,
>
> Thanks for the answer. I have also been bitten by the byte/bit bug in the past but in this case it must be something different. All my values are in in the correct amount of bits.
>
> The most important problem is actually problem 2: why does the tc toward internet (dev WAN) do what it does?
>
>
> Groeten,
>
> Joost Kraaijeveld
> Askesis B.V.
> Molukkenstraat 14
> 6524NB Nijmegen
> tel: 024-3888063 / 06-51855277
> fax: 024-3608416
> e-mail: J.Kraaijeveld@Askesis.nl
> web: www.askesis.nl
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-08-05 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 7:53 [LARTC] TC-ng questions/problems Joost Kraaijeveld
2004-08-05 8:12 ` lartc
2004-08-05 8:26 ` Joost Kraaijeveld
2004-08-05 9:59 ` lartc [this message]
2004-08-05 10:36 ` Joost Kraaijeveld
2004-08-05 20:06 ` Stef Coene
2004-08-06 8:54 ` lartc
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=1091699959.13878.4.camel@drs0 \
--to=lartc@manchotnetworks.net \
--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.