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] Bandwidth management under linux
Date: Thu, 13 Jan 2005 14:07:41 +0000	[thread overview]
Message-ID: <200501131507.41996.stef.coene@docum.org> (raw)
In-Reply-To: <8105747b0501130502342acdca@mail.gmail.com>

On Thursday 13 January 2005 14:02, Johan Jordaan wrote:
> In my search to control bandwidth on my network I found 2 projects..
>
> 1. TC
> 2. BWM Tools - http://freshmeat.net/projects/bwmtools/
>
> This brings me to 2 questions...
>
> Firstly, can TC control bandwidth in both directions?
It can shape outgoing traffic.  If you have 2 network cards, you can shape in 
bothe directions.  But it can also throtlle incoming traffic if you want 
(this is not so powerfull as shaping outgoing traffic).

> I read that it 
> can only do 1 direction, which one I cant remember. 
Outgoing.

> Can you monitor 
> the load on the queues you define?
Yes, with external scripting.

> Does TC support IPv6? 
Yes (I think)

> Secondly, BWM Tools seems to queue traffic to userspace and use some
> kind of kernel module to allow it through or not. How efficient is
> bandwidth control using ip queing to userspace? BWM Tools doesn't seem
> to support IPv6  :(
I don't know how BWM works.


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

      parent reply	other threads:[~2005-01-13 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13 13:02 [LARTC] Bandwidth management under linux Johan Jordaan
2005-01-13 13:02 ` Johan Jordaan
2005-01-13 13:25 ` Arjan van de Ven
2005-01-13 13:44 ` Michele Mordenti
2005-01-13 14:07 ` Stef Coene [this message]

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=200501131507.41996.stef.coene@docum.org \
    --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.