On Tue Oct 06 2020, Vladimir Oltean wrote:
> On Tue, Oct 06, 2020 at 03:23:36PM +0200, Kurt Kanzenbach wrote:
>> So you're saying private VLANs can be used but the user or the other
>> kernel modules shouldn't be allowed to use them to simplify the
>> implementation? Makes sense to me.
>
> It would be interesting to see if you could simply turn off VLAN
> awareness in standalone mode, and still use unique pvids per port.
That doesn't work, just tested. When VLAN awareness is disabled,
everything is switched regardless of VLAN tags and table. Therefore, the
implementation could look like this:
* bridge without filtering:
* vlan_awareness=0
* drop private vlans
* bridge with vlan filtering:
* vlan_awareness=1
* drop private vlans
* standalone:
* vlan_awareness=1
* use private vlans
* forbid other users to use private vlans to allow
configure_vlans_while_not_filtering behavior in .vlan_prepare()
* forbid use of lan0.<X> and lan1.<X> in .port_prechangeupper()
So, this should work, or?
Thanks,
Kurt
Attachment:
signature.asc
Description: PGP signature
