All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerardo Arceri <elfarto@elfarto.com.ar>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems with HTB (ceil being overpassed)
Date: Thu, 29 Jan 2004 20:41:03 +0000	[thread overview]
Message-ID: <opr2j02psh4ddcy3@mail.elfarto.com.ar> (raw)
In-Reply-To: <opr2glxzfo4ddcy3@mail.elfarto.com.ar>

You were right thanks for the tip, i suspected there was some clock issue 
involved, now it works perfectly, 2500Kbit limit is not passed by a single 
byte... superb, thanks again.!


On Wed, 28 Jan 2004 00:20:13 -0200 (BRST), <rubens@etica.net> wrote:

>
> It seems you have hit timer innacuracy issues:
> http://www.docum.org/stef.coene/qos/faq/cache/40.html
>
> Rubens
>
>
> On Tue, 27 Jan 2004, Gerardo Arceri wrote:
>
>> We run a Hosting farm behind a bridge/iptables firewall setup running
>> Gentoo with kernel 2.4.20-gentoo-r6, connected to a dual 15Mbps
>> international internet pipe / , as this:
>>
>> Net Pipe --------- eth1 Bridge/Firewall eth0 -------- Internal Hosting
>> Network
>>
>> lately we have been looking at htb to somehow control excessive usage 
>> from
>> the users behind, but in our implementation there seems to be an error 
>> or
>> something wrong on the setup,
>> this is the test script i'm using, i know it's very rough but i think it
>> should do the work.
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

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

  parent reply	other threads:[~2004-01-29 20:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28  0:21 [LARTC] Problems with HTB (ceil being overpassed) Gerardo Arceri
2004-01-28  2:20 ` rubens
2004-01-29 20:41 ` Gerardo Arceri [this message]
2004-01-29 21:07 ` Gerardo Arceri
2004-02-03 23:21 ` miller69

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=opr2j02psh4ddcy3@mail.elfarto.com.ar \
    --to=elfarto@elfarto.com.ar \
    --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.