From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bridging and shaping
Date: Wed, 25 Sep 2002 07:56:58 +0000 [thread overview]
Message-ID: <marc-lartc-103294072100637@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103293334928340@msgid-missing>
On Wednesday 25 September 2002 07:59, Rohan Almeida wrote:
> Hi List,
>
> I've truly sorry if this question has been tried
> on this LIST, but i'm quite desperate now!
>
> I'm currently using a linux box doing proxy-arp,
> with same IP on both interfaces.
> kernel 2.4.18 with htb and iproute2 patch
> iptables and tc works perfectly as expected
>
> Now, I want to convert the linux box to a
> bridge, using (http://bridge.sourceforge.net)
This code is already available in kernel 2.4.x, so no patches needed if you
use a 2.4.x kernel.
> I noticed that you have to patch the kernel
> as well as iptables.
It's only needed to patch the kernel if you want to use iptables on the
bridge.
> Does tc need to be patched?
No
> Does this even work?
Yes
> I mean is it possible to operate linux
> in bridge mode and have bandwidth control also?
Yes. You can use the u32 filter. If you want to use the iptables+fw-filter,
you will need extra patches.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-09-25 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 5:55 [LARTC] bridging and shaping Rohan Almeida
2002-09-25 7:56 ` Stef Coene [this message]
2002-09-25 12:50 ` Julio E. Gonzalez P.
2002-09-25 15:39 ` Stef Coene
2002-09-28 13:04 ` Jens Link
2002-09-28 13:50 ` Jens Link
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-103294072100637@msgid-missing \
--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.