From: jhautbois@gmail.com
To: Ross Vandegrift <ross@kallisti.us>,
Jean-Michel Hautbois <jhautbois@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: [Bridge] Re :Re: Bridging LACP (802.3ad) frames not working
Date: Tue, 12 Jan 2010 15:28:53 +0000 [thread overview]
Message-ID: <001485e72564c1387e047cf94f54@google.com> (raw)
In-Reply-To: <20100112152317.GB23219@kallisti.us>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Hi Ross,
Le 12 janv. 2010 16:23, Ross Vandegrift <ross@kallisti.us> a écrit :
> You can't bridge LACP - it doesn't even make sense. LACP bundles must
> be between adjacent devices. Moreover, LACPDUs are destined for a
> bridge-management address that is prohibited from being bridged by
> 802.1D.
OK, I agree, it doesn't make sense, but I want to be transparent using
bridging. I can't explain my idea :).
> What are you trying to accomplish? If you want to transparently
> bridge with LACP channels, you should terminate the LACP bundles on
> the Linux box and bridge the bundles:
> eth0 \ / eth2
> bond0 ----- br0 ---- bond1
> eth1 / \ eth3
You mean I need to have four physical interfaces ?
I can't understand how too accomplish this.
Currently, I am doing :
brctl addif eth1
brctl addif eth2
> And then cable eth0/eth1 to one device and eth2/eth3 to the other.
How ?
Thanks !
JM
[-- Attachment #2: Type: text/html, Size: 1284 bytes --]
next prev parent reply other threads:[~2010-01-12 15:28 UTC|newest]
Thread overview: 8+ 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 ` jhautbois [this message]
2010-01-12 21:32 ` [Bridge] Re :Re: " Ross Vandegrift
2010-01-12 21:40 ` [Bridge] Re :Re: " jhautbois
2010-01-12 22:04 ` Ross Vandegrift
2010-01-13 0:40 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2010-01-12 19:44 [Bridge] " Jean-Michel Hautbois
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=001485e72564c1387e047cf94f54@google.com \
--to=jhautbois@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=ross@kallisti.us \
/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