From: "S Mohan" <smohan@vsnl.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] QoS on bridge device
Date: Tue, 04 Mar 2003 13:41:32 +0000 [thread overview]
Message-ID: <marc-lartc-104678495206038@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104676864925112@msgid-missing>
The packet flow diagrams have been well documented here.
http://users.pandora.be/bart.de.schuymer/ebtables/br_fw_ia/br_fw_ia.html
If you are matching packets for shaping, you must use tc. iptables will not
do any shaping. It will only modify headers and take decision on packet
flow. The only place where this would be amenable to any kind of traffic
management is rate limiting. This is not in any place/ application
constitute/construe bandwidth management or traffic shaping.
Mohan
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]On
Behalf Of Abraham van der Merwe
Sent: 04 March 2003 18:36
To: Bogdan Coman
Cc: Linux Advanced Routing & Traffic Control list
Subject: Re: [LARTC] QoS on bridge device
Hi Bogdan!
Thanks. One more question:
If I match packets for shaping (instead of tc filters), which chain should I
match packets on? Usually I use FORWARD in the mangle table, but if I look
at the following diagram:
http://www.sparkle-cc.co.uk/firewall/firewall.html
it seems that packets won't go through FORWARD anymore (if it goes through
the bridge) so I guess I should match packets on OUTPUT in the mangle table
- is this assumption correct?
> The shaping is done on eth0 and eth1. There is also a patch that allows
> you to match packets that are passing the bridge with iptables. Br0 is
> used only for trafic that is for the bridge. Eg. a machine has a route
> through the ip of br0.
>
> Bogdan Coman
>
> On Tue, 2003-03-04 at 10:58, Abraham van der Merwe wrote:
> > Hi!
> >
> > Usually if you have a machine and traffic passes through it:
> >
> > +-----+
> > eth0| QoS |
> > -------------| box |-------------
> > | |eth1
> > +-----+
> >
> > You can shape outgoing traffic on eth0 and eth1 effectively shaping both
> > incoming/outgoing traffic.
> >
> > With bridging and above setup you only have a single device br0 - my
> > question is whether you can shape both incoming/outgoing traffic on this
> > device (i would presume it is not possible) or do you need to redirect
> > traffic passing through br0 to imq0 and do shaping on outgoing traffic
on
> > both br0 and imq0?
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
--
Regards
Abraham
I'm not sure whether that's actually useful...
-- Larry Wall in <199710011704.KAA21395@wall.org>
___________________________________________________
Abraham vd Merwe [ZR1BBQ] - Frogfoot Networks
P.O. Box 3472, Matieland, Stellenbosch, 7602
Cell: +27 82 565 4451 Http: http://www.frogfoot.net/
Email: abz@frogfoot.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:[~2003-03-04 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 8:58 [LARTC] QoS on bridge device Abraham van der Merwe
2003-03-04 9:25 ` S Mohan
2003-03-04 9:43 ` Bogdan Coman
2003-03-04 13:06 ` Abraham van der Merwe
2003-03-04 13:41 ` S Mohan [this message]
2003-03-04 13:58 ` Abraham van der Merwe
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-104678495206038@msgid-missing \
--to=smohan@vsnl.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.