On Fri, Oct 16, 2020 at 09:56:22AM -0700, Florian Fainelli wrote: > I probably missed parts of this long discussion, but for this generation > of switches, does that mean that you will only allow a bridge with > vlan_filtering=1 to be configured and also refuse toggling of > vlan_filtering at run time? No, the bridge vlan_filtering option will be supported as both on or off. The limitation that you're probably thinking of is that NETIF_F_HW_VLAN_CTAG_FILTER will be non-optionally forced on. Otherwise stated, ports in standalone mode will drop VLAN-tagged traffic unless they have an 8021q upper with that VLAN ID. Which is probably ok considering that the network stack would drop them anyway in absence of an 8021q upper, but they won't be visible in tcpdump either, as things stand. Otherwise stated, standalone hellcreek ports cannot support promiscuous mode. I know that currently DSA sets up NETIF_F_HW_VLAN_CTAG_FILTER as forced-on for everybody, but that limitation could be lifted for some switches, but not for hellcreek. Just something to keep in mind.
