From: Abraham van der Merwe <abz@frogfoot.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] QoS on bridge device
Date: Tue, 04 Mar 2003 13:58:39 +0000 [thread overview]
Message-ID: <marc-lartc-104678683407900@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104676864925112@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
Hi S!
> The packet flow diagrams have been well documented here.
> http://users.pandora.be/bart.de.schuymer/ebtables/br_fw_ia/br_fw_ia.html
That assumes you're using ebtables and matching traffic passing through br0.
I want to match traffic passing through eth0 and eth1.
> 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.
Yes, I know. tc matches traffic according to flags set in skb->priority. I'm
using iptables to match traffic and set those priorities (so like I said I'm
not using tc filters - i'm still using tc qdiscs to do the actual shaping).
--
Regards
Abraham
"I prefer rogues to imbeciles, because they sometimes take a rest."
-- Alexandre Dumas (fils)
___________________________________________________
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
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2003-03-04 13:58 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
2003-03-04 13:58 ` Abraham van der Merwe [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=marc-lartc-104678683407900@msgid-missing \
--to=abz@frogfoot.net \
--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.