From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bandwidth control question.
Date: Mon, 10 Mar 2003 14:52:58 +0000 [thread overview]
Message-ID: <marc-lartc-104730808930470@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104730778030078@msgid-missing>
Yes,
You can use tc on a bridge. See also this thread:
http://mailman.ds9a.nl/pipermail/lartc/2003q1/007378.html
If you are just going to perform traffic control, and you don't need to
use iptables, you don't need the bridge+nf functionality.
Add your filters to the "real" devices, not br0.
-Martin
: I'm looking for a way to limit bandwidth to/from clients using a
: contended 2Mb link. What I'm looking for is to allow a client machine to
: use the full 2Mb but only if there is no traffic to/from other clients.
: I've been looking at htb.init and cbq.init, and believe that the BURST
: used in htb.init will allow what I need.
:
: I'm looking to put in place something like:
: ------------------
: | Router |
: ------------------
: |
: ------------------
: | Bridge |
: ------------------
: |
: ------------------
: | Switch |
: ------------------
: |
: Various servers
:
: Am I right in thinking that I'll be able to use tc within the bridge ?
:
: Regards,
: Jon
:
: _______________________________________________
: LARTC mailing list / LARTC@mailman.ds9a.nl
: http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
:
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
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-03-10 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 14:48 [LARTC] bandwidth control question Jon Lawrence
2003-03-10 14:52 ` Martin A. Brown [this message]
2003-03-10 17:36 ` Stef Coene
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-104730808930470@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--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.