From: Sebastian Arcus <shop@open-t.co.uk>
To: lartc@vger.kernel.org
Subject: Re: Egress bandwidth limiting not working?
Date: Wed, 08 May 2013 18:29:57 +0000 [thread overview]
Message-ID: <518A99A5.4070101@open-t.co.uk> (raw)
In-Reply-To: <5188DD0D.4020708@open-t.co.uk>
On 08/05/13 18:24, Andrew Beverley wrote:
> On Wed, 2013-05-08 at 08:03 +0100, Sebastian Arcus wrote:
>>> Are you just trying to achieve simple policing of the interface, or
>>> something more advanced?
>>>
>>
>> Thanks Andrew. I'm only trying to achieve bandwidth limitation and QoS
>> priority for some VoIP traffic.
>
> Yeah, I would just try HTB then. It's not the easiest either, but follow
> some examples and you should be fine.
I have tried the HTB example here:
http://www.lartc.org/howto/lartc.cookbook.ultimate-tc.html and it seems
to work fine - it certainly limits the bandwidth in both directions.
Thanks again for that.
The one thing to watch out for is
> that the sum of the bandwidth for all the leaf classes should add up to
> the bandwidth of the root class.
In that case is the HTB example in the LARTC cookbook
(http://www.lartc.org/howto/lartc.cookbook.ultimate-tc.html) wrong? It
assigns to the first leaf class 100% of parent bandwidth, and to the
second 90% of it.
>
> My example is at:
>
> http://andybev.com/index.php/Fair_traffic_shaping_an_ADSL_line_for_a_local_network_using_Linux
>
> [...]
>
>> and the HTB section hints to the need to patch the kernel - which put
>> me off at the time.
>
> It's now in the vanilla kernel, so a lot easier :)
It seems that HTB was added to the kernel in 2.4.20! - so it would be
nice if somebody with access to LARTC.org would amend the mention about
kernel patching on the page above. Also, it would be useful if the same
page would mention that HTB is preferable and simpler than CBQ.
next prev parent reply other threads:[~2013-05-08 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 10:53 Egress bandwidth limiting not working? Sebastian Arcus
2013-05-08 6:10 ` Andrew Beverley
2013-05-08 7:03 ` Sebastian Arcus
2013-05-08 17:24 ` Andrew Beverley
2013-05-08 18:29 ` Sebastian Arcus [this message]
2013-05-14 19:38 ` Andrew Beverley
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=518A99A5.4070101@open-t.co.uk \
--to=shop@open-t.co.uk \
--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.