You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
This issue it to implement VLAN trunking support in Linux bridging. As the implementation of QinQ uses this bridge functionality we will implement support for it in this issue.
Use case
This will allow to restrict the VLANs that a VM can access to and use trunking mode in a secure way, as we'll as easily define QinQ networks.
Interface Changes
The implementation should use the attributes already present in OpenvSwitch
VLAN trunking, uses VLAN_TAGGED_ID to specify a range of VLANs to tag, for example: 1,10,30,32,100-200.
QinQ uses 2 different attributes to set the customer and service vlan ids:
CVLANS Customer VLAN IDs, as a comma separated list
VLAN_ID Service 802.1Q VLAN ID. (current setting)
Additional Context
A different feature will address access control to the VLAN sets
Progress Status
Code committed
Testing - QA
Documentation (Release notes - resolved issues, compatibility, known issues)
The text was updated successfully, but these errors were encountered:
Description
This issue it to implement VLAN trunking support in Linux bridging. As the implementation of QinQ uses this bridge functionality we will implement support for it in this issue.
Use case
This will allow to restrict the VLANs that a VM can access to and use trunking mode in a secure way, as we'll as easily define QinQ networks.
Interface Changes
The implementation should use the attributes already present in OpenvSwitch
VLAN_TAGGED_ID
to specify a range of VLANs to tag, for example: 1,10,30,32,100-200.CVLANS
Customer VLAN IDs, as a comma separated listVLAN_ID
Service 802.1Q VLAN ID. (current setting)Additional Context
A different feature will address access control to the VLAN sets
Progress Status
The text was updated successfully, but these errors were encountered: