Hi all,
I'm aware this has been covered in previous threads, but no real answers were given.
I have been using Proxmox for a while, and always used with openvswitch. I've got a use case (hypervisors used for tenanted VNFs) where I need to have a single virtual NIC with specific VLAN tags in the GUI.
I understand that not specifying a VLAN on the GUI will essentially trunk all VLANs, however my use case needs specific VLANs, and we can't really scale multiple NICs well due to VNF interface limitations.
The OVS syntax itself is very simple: instead of tag=50 it's trunk=5,50,500. It would also seem there is already functionality in the Proxmox backend for this https://pve.proxmox.com/wiki/Manual:_qm.conf.
How difficult would it be to get a GUI modification on this? I'm interested to the point I'm happy paying for development time for this feature, as long as it can be merged into one of the next updates.
REgards,
I'm aware this has been covered in previous threads, but no real answers were given.
I have been using Proxmox for a while, and always used with openvswitch. I've got a use case (hypervisors used for tenanted VNFs) where I need to have a single virtual NIC with specific VLAN tags in the GUI.
I understand that not specifying a VLAN on the GUI will essentially trunk all VLANs, however my use case needs specific VLANs, and we can't really scale multiple NICs well due to VNF interface limitations.
The OVS syntax itself is very simple: instead of tag=50 it's trunk=5,50,500. It would also seem there is already functionality in the Proxmox backend for this https://pve.proxmox.com/wiki/Manual:_qm.conf.
How difficult would it be to get a GUI modification on this? I'm interested to the point I'm happy paying for development time for this feature, as long as it can be merged into one of the next updates.
REgards,