Hi, this is a rework of vlan && qinq plugin to always use a vnet bridge for all plugin.
Avoid to tag vmport directly on vlan-aware bridge or ovs. Instead, plug the vm interface on a vnet bridge, and plug the vnet bridge on the ovs|bridge-vlan-aware|... and do the tag here. This will help a lot of handling tag modification on a vnet, as we don't defined tap|veth in /etc/network/interfaces, and make same vnet model for each plugins. Qinq plugin was buggy, I have fixed it and added support for ovs+classic linux bridge. I have also added vlan-protocol option back, to handle both 802.1ad && 802.1q service vlan. I'll update documentation && gui tomorrow Alexandre Derumier (7): don't sort interfaces in /etc/network/interfaces.d/sdn restrict zone name to 8 characters retrict vnet name to 8 characters vlan: use new model qinq: use new model + ovs/classic bridge support evpn: prefix interfaces vxlan: prefix interfaces PVE/Network/SDN/Controllers/EvpnPlugin.pm | 2 +- PVE/Network/SDN/VnetPlugin.pm | 2 +- PVE/Network/SDN/Zones.pm | 2 +- PVE/Network/SDN/Zones/EvpnPlugin.pm | 24 ++-- PVE/Network/SDN/Zones/Plugin.pm | 2 +- PVE/Network/SDN/Zones/QinQPlugin.pm | 133 +++++++++++++++++----- PVE/Network/SDN/Zones/VlanPlugin.pm | 90 ++++++++++----- PVE/Network/SDN/Zones/VxlanPlugin.pm | 6 +- 8 files changed, 184 insertions(+), 77 deletions(-) -- 2.20.1 _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
