From: Ross Vandegrift <ross@kallisti.us>
To: jhautbois@gmail.com
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working
Date: Tue, 12 Jan 2010 17:04:48 -0500 [thread overview]
Message-ID: <20100112220448.GF23219@kallisti.us> (raw)
In-Reply-To: <001485f790a4c2633c047cfe80e0@google.com>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
On Tue, Jan 12, 2010 at 09:40:30PM +0000, jhautbois@gmail.com wrote:
> This is exactly the problem.
> But, sounds like it is not possible... ?
You could run a custom version of the bridge driver to enable bridging
of frames sent to the bridge-management MAC addresses. Some folks
have talked about doing similar things to enable bridging of STP.
Doing that with STP makes a bit more sense to me (since there are
valid networks that could be constructed that way). But you'll be
breaking a pretty fundamental assumption of LACP....
--
Ross Vandegrift
ross@kallisti.us
"If the fight gets hot, the songs get hotter. If the going gets tough,
the songs get tougher."
--Woody Guthrie
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-01-12 22:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 15:13 [Bridge] Bridging LACP (802.3ad) frames not working Jean-Michel Hautbois
2010-01-12 15:23 ` Ross Vandegrift
2010-01-12 15:28 ` [Bridge] Re :Re: " jhautbois
2010-01-12 21:32 ` Ross Vandegrift
2010-01-12 21:40 ` [Bridge] Re :Re: " jhautbois
2010-01-12 22:04 ` Ross Vandegrift [this message]
2010-01-13 0:40 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2010-01-12 22:58 richardvoigt
2010-01-13 9:26 ` Jean-Michel Hautbois
2010-01-13 10:29 Jean-Michel Hautbois
2010-01-13 16:30 ` Stephen Hemminger
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=20100112220448.GF23219@kallisti.us \
--to=ross@kallisti.us \
--cc=bridge@lists.linux-foundation.org \
--cc=jhautbois@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox