* [Bridge] Bridging LACP (802.3ad) frames not working
@ 2010-01-12 15:13 Jean-Michel Hautbois
2010-01-12 15:23 ` Ross Vandegrift
0 siblings, 1 reply; 11+ messages in thread
From: Jean-Michel Hautbois @ 2010-01-12 15:13 UTC (permalink / raw)
To: bridge
Hi there !
I have connected two ethernet 1000Mbps interfaces to my routers, and I
have built a bridge between them :
eth1 <---> br0 <---> eth2
When I am transmitting UDP, ADP, ARP or any other type of frames, I
don't have any problem.
But when, the router sends LACP packets, it is not transmitted
(neither from eth1 to eth2 than from eth2 to eth1).
I can't figure out why, so if you have an idea, thanks in advance for
your help !
Best Regards !
JM
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bridge] Bridging LACP (802.3ad) frames not working
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
0 siblings, 1 reply; 11+ messages in thread
From: Ross Vandegrift @ 2010-01-12 15:23 UTC (permalink / raw)
To: Jean-Michel Hautbois; +Cc: bridge
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
On Tue, Jan 12, 2010 at 04:13:01PM +0100, Jean-Michel Hautbois wrote:
> Hi there !
>
> I have connected two ethernet 1000Mbps interfaces to my routers, and I
> have built a bridge between them :
> eth1 <---> br0 <---> eth2
>
> When I am transmitting UDP, ADP, ARP or any other type of frames, I
> don't have any problem.
> But when, the router sends LACP packets, it is not transmitted
> (neither from eth1 to eth2 than from eth2 to eth1).
>
> I can't figure out why, so if you have an idea, thanks in advance for
> your help !
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.
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
And then cable eth0/eth1 to one device and eth2/eth3 to the other.
Ross
--
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 --]
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bridge] Re :Re: Bridging LACP (802.3ad) frames not working
2010-01-12 15:23 ` Ross Vandegrift
@ 2010-01-12 15:28 ` jhautbois
2010-01-12 21:32 ` Ross Vandegrift
0 siblings, 1 reply; 11+ messages in thread
From: jhautbois @ 2010-01-12 15:28 UTC (permalink / raw)
To: Ross Vandegrift, Jean-Michel Hautbois; +Cc: bridge
[-- 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 --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bridge] Re :Re: Bridging LACP (802.3ad) frames not working
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
0 siblings, 1 reply; 11+ messages in thread
From: Ross Vandegrift @ 2010-01-12 21:32 UTC (permalink / raw)
To: jhautbois; +Cc: bridge
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
On Tue, Jan 12, 2010 at 03:28:53PM +0000, jhautbois@gmail.com wrote:
> OK, I agree, it doesn't make sense, but I want to be transparent using
> bridging. I can't explain my idea :).
You can't be transparent with respect to LACP if you're using ethernet
to bridge. It doesn't make sense - LACP is negotiated between bridge
ports on a point-to-point ethernet interface.
> 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
No - you don't need four physical interfaces. I was trying to
extrapolate what problem you might be trying to solve, and I think I
guessed wrong. I imagined that you needed a multi-interface bundle
through a Linux bridge.
If you just want your box to speak LACP to the adjacent switches, you
could easily make bond interfaces with single ethernet interfaces.
But it sounds like you don't want to speak LACP to the switches, you
want to pass it as if you were a layer 1 device.
Ross
--
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 --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bridge] Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working
2010-01-12 21:32 ` Ross Vandegrift
@ 2010-01-12 21:40 ` jhautbois
2010-01-12 22:04 ` Ross Vandegrift
0 siblings, 1 reply; 11+ messages in thread
From: jhautbois @ 2010-01-12 21:40 UTC (permalink / raw)
To: Ross Vandegrift, jhautbois; +Cc: bridge
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
Le , Ross Vandegrift <ross@kallisti.us> a écrit :
> On Tue, Jan 12, 2010 at 03:28:53PM +0000, jhautbois@gmail.com wrote:
> > OK, I agree, it doesn't make sense, but I want to be transparent using
> > bridging. I can't explain my idea :).
> You can't be transparent with respect to LACP if you're using ethernet
> to bridge. It doesn't make sense - LACP is negotiated between bridge
> ports on a point-to-point ethernet interface.
> > 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
> No - you don't need four physical interfaces. I was trying to
> extrapolate what problem you might be trying to solve, and I think I
> guessed wrong. I imagined that you needed a multi-interface bundle
> through a Linux bridge.
> If you just want your box to speak LACP to the adjacent switches, you
> could easily make bond interfaces with single ethernet interfaces.
> But it sounds like you don't want to speak LACP to the switches, you
> want to pass it as if you were a layer 1 device.
This is exactly the problem.
But, sounds like it is not possible... ?
JM
[-- Attachment #2: Type: text/html, Size: 1706 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bridge] Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working
2010-01-12 21:40 ` [Bridge] Re :Re: " jhautbois
@ 2010-01-12 22:04 ` Ross Vandegrift
2010-01-13 0:40 ` Stephen Hemminger
0 siblings, 1 reply; 11+ messages in thread
From: Ross Vandegrift @ 2010-01-12 22:04 UTC (permalink / raw)
To: jhautbois; +Cc: bridge
[-- 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 --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bridge] Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working
2010-01-12 22:04 ` Ross Vandegrift
@ 2010-01-13 0:40 ` Stephen Hemminger
0 siblings, 0 replies; 11+ messages in thread
From: Stephen Hemminger @ 2010-01-13 0:40 UTC (permalink / raw)
To: Ross Vandegrift; +Cc: bridge
On Tue, 12 Jan 2010 17:04:48 -0500
Ross Vandegrift <ross@kallisti.us> wrote:
> 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....
Recent kernels will forward link local frames as long as STP is disabled.
Older kernels will not.
The assumption is that if STP is enabled, then it will be managing
control plane.
Author: Stephen Hemminger <shemminger@vyatta.com> 2009-05-14 23:10:13
Committer: David S. Miller <davem@davemloft.net> 2009-05-17 21:12:54
Parent: 43aa1920117801fe9ae3d1fad886b62511e09bee (bridge: handle process all link-local frames)
Branches: master, remotes/origin/master
Follows: v2.6.30-rc6
Precedes: v2.6.30-rc7
bridge: relay bridge multicast pkgs if !STP
Currently the bridge catches all STP packets; even if STP is turned
off. This prevents other systems (which do have STP turned on)
from being able to detect loops in the network.
With this patch, if STP is off, then any packet sent to the STP
multicast group address is forwarded to all ports.
Based on earlier patch by Joakim Tjernlund with changes
to go through forwarding (not local chain), and optimization
that only last octet needs to be checked.
Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
--
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bridge] Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working
@ 2010-01-12 22:58 richardvoigt
2010-01-13 9:26 ` Jean-Michel Hautbois
0 siblings, 1 reply; 11+ messages in thread
From: richardvoigt @ 2010-01-12 22:58 UTC (permalink / raw)
To: Ross Vandegrift; +Cc: bridge
On Tue, Jan 12, 2010 at 4:04 PM, Ross Vandegrift <ross@kallisti.us> wrote:
> 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....
LACP is between peers, not to the nearest connected device (generally
an ethernet cable). As long as the intermediate link acts just like a
wire and passes everything, LACP shouldn't care. And there are some
reasonable cases to want a Linux box to look like a piece of cable
(e.g. wiretap, timed lockdown, satellite network simulator which
inserts delay and errors, etc.) to the surrounding network. Of
course, whether seeing just one link out of an aggregation bundle is
useful is debatable, but Linux ought to be able to support it. I've
been bitten before by adding a new switch into an STP setup and having
it eat STP packets even though STP processing was disabled. So count
me as another vote for (at least the possibility of) layer 1-esque
transparent bridging.
>
> --
> 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
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAktM8gAACgkQMlMoONfO+HC6UwCgkLsC/ZE4ovcxX1e+A/NV3ELz
> Rp4AoIFyCMtgrMYkxK2k81b9M3n6/v0U
> =A5kn
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bridge] Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working
2010-01-12 22:58 richardvoigt
@ 2010-01-13 9:26 ` Jean-Michel Hautbois
0 siblings, 0 replies; 11+ messages in thread
From: Jean-Michel Hautbois @ 2010-01-13 9:26 UTC (permalink / raw)
To: richardvoigt@gmail.com; +Cc: bridge
2010/1/12 richardvoigt@gmail.com <richardvoigt@gmail.com>:
> On Tue, Jan 12, 2010 at 4:04 PM, Ross Vandegrift <ross@kallisti.us> wrote:
>> 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....
>
> LACP is between peers, not to the nearest connected device (generally
> an ethernet cable). As long as the intermediate link acts just like a
> wire and passes everything, LACP shouldn't care. And there are some
> reasonable cases to want a Linux box to look like a piece of cable
> (e.g. wiretap, timed lockdown, satellite network simulator which
> inserts delay and errors, etc.) to the surrounding network. Of
> course, whether seeing just one link out of an aggregation bundle is
> useful is debatable, but Linux ought to be able to support it. I've
> been bitten before by adding a new switch into an STP setup and having
> it eat STP packets even though STP processing was disabled. So count
> me as another vote for (at least the possibility of) layer 1-esque
> transparent bridging.
I think it would be interesting to have the ability to activate this
functionality.
AFAIK, this could be done in the br_handle_frame function, testing the
skb->protocol and comparing it with ETH_P_SLOW. This could be
conditionned by a flag, and this flag would be unabled by default.
Why is this a problem ?
If you tell this is not good, unless you know what you are doing,
where is the problem ?
This is a user problem, it is a functionality. If you misuse it, this
is not a kernel problem...
Best Regards,
JM
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bridge] Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working
@ 2010-01-13 10:29 Jean-Michel Hautbois
2010-01-13 16:30 ` Stephen Hemminger
0 siblings, 1 reply; 11+ messages in thread
From: Jean-Michel Hautbois @ 2010-01-13 10:29 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: bridge
2010/1/13 Stephen Hemminger <shemminger@vyatta.com>:
> On Tue, 12 Jan 2010 17:04:48 -0500
> Ross Vandegrift <ross@kallisti.us> wrote:
>
>> 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....
>
> Recent kernels will forward link local frames as long as STP is disabled.
> Older kernels will not.
>
> The assumption is that if STP is enabled, then it will be managing
> control plane.
Well, I have a 2.6.31 kernel. And LACP is not forwarded, even when STP
is disabled.
I don't understand what you mean ?
JM
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bridge] Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working
2010-01-13 10:29 Jean-Michel Hautbois
@ 2010-01-13 16:30 ` Stephen Hemminger
0 siblings, 0 replies; 11+ messages in thread
From: Stephen Hemminger @ 2010-01-13 16:30 UTC (permalink / raw)
To: Jean-Michel Hautbois; +Cc: bridge
On Wed, 13 Jan 2010 11:29:55 +0100
Jean-Michel Hautbois <jhautbois@gmail.com> wrote:
> 2010/1/13 Stephen Hemminger <shemminger@vyatta.com>:
> > On Tue, 12 Jan 2010 17:04:48 -0500
> > Ross Vandegrift <ross@kallisti.us> wrote:
> >
> >> 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....
> >
> > Recent kernels will forward link local frames as long as STP is disabled.
> > Older kernels will not.
> >
> > The assumption is that if STP is enabled, then it will be managing
> > control plane.
>
> Well, I have a 2.6.31 kernel. And LACP is not forwarded, even when STP
> is disabled.
> I don't understand what you mean ?
I meant they get processed locally, before that they were dropped.
The best solution is to write an ebtables rule to forward them.
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2010-01-13 16:30 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
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.