I will take a look. I have tested on a number of different versions,
but nothing as new as 4.11, only been tracking the shipped kernel with
Ubuntu 14.04 and 16.04, in the 3.1 and 4.4 versions respectively, but
pulling from upstream and compiling from source instead of Ubuntu src
packages.
-C
On 06/28/2017 12:09 AM, Vincent Bernat wrote:
❦ 27 juin 2017 23:26 -0700, Chris Burton <chris.bur...@speakeasy.net> :
Interesting, in the kernel versions I tested I was not able to get it
to work by just passing in the runtime changes to
/sys/class/net/<bridge>/bridge/group_fwd_mask, I actually had to make
changes to virtual bridge header file and recompile the kernel as
there are/were safeguards in place to prevent someone from just making
the runtime changes, which makes sense because this is a potentially
dangerous change. Recompiling is not a big deal, but would be
interested to know which kernel versions you were able to get that to
work with just runtime changes as that would save some time.
The different cases are handled here:
http://elixir.free-electrons.com/linux/v4.11.5/source/net/bridge/br_input.c#L275
fwd_mask_required is not tunable by the user. Unless you are using
VLAN-aware bridges _and_ QinQ, its value is 0. group_fwd_mask is the
live value you put in sysfs, so it should work. There is a safeguard
mechanism to deny acceptance of 01-80-C2-00-00-[00,0B,0C,0D,0F] when
setting the group_fwd_mask value.
I didn't test recently, but I have used this mechanism in the past for
LLDP. Which kernel are you using?
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
