[j-nsp] LACP is not running between two VMX

[Vincent Bernat]

 ❦ 25 avril 2019 09:31 +01, <adamv0025 at netconsultings.com>:

> I haven't tried MC-LAG, but I used standard LAG (with LACP).
> The problem I faced was that the standard Linux bridges (usually used to
> simulate virtual p2p links between vMX-es won't forward BPDUs including LACP
> (and I did not find a way to hack around at that time)

You can play with /sys/class/net/br0/bridge/group_fwd_mask. Well, in
fact, you can't:

hat:		/sys/class/net/<bridge iface>/bridge/group_fwd_mask
Date:		January 2012
KernelVersion:	3.2
Contact:	netdev at vger.kernel.org
Description:
		Bitmask to allow forwarding of link local frames with address
		01-80-C2-00-00-0X on a bridge device. Only values that set bits
		not matching BR_GROUPFWD_RESTRICTED in net/bridge/br_private.h
		allowed.
		Default value 0 does not forward any link local frames.

		Restricted bits:
		0: 01-80-C2-00-00-00 Bridge Group Address used for STP
		1: 01-80-C2-00-00-01 (MAC Control) 802.3 used for MAC PAUSE
		2: 01-80-C2-00-00-02 (Link Aggregation) 802.3ad

		Any values not setting these bits can be used. Take special
                care when forwarding control frames e.g. 802.1X-PAE or LLDP.
-- 
Go not to the elves for counsel, for they will say both yes and no.
		-- J.R.R. Tolkien