Improve VLAN support and Service Binding

Feature Request
1

Having come from Proxmox, I have found the Networking Config in QNAP somewhat frustrating…

  1. In single QNAP NIC configuration (e.g TS-462a) creation of a switch for the native network prevents additional switches for other VLANs

  2. Service Binding can’t be enabled in a single NIC configuration, but Service Binding for vSwitches on different VLANs makes sense

  3. Service Binding is enabled on a per physical NIC with binding on different VLANs/switches buried in the separate Service Settings (e.g. SMB)

  4. “Software defined switch” means something completely different in the I.T. industry - I think you mean private/internal switch?

  5. It would be better to integrate the VLAN setting in the vSwitch settings rather than with the NICs

For reference (I’m a retired I.T. Sys Admin, so…) I have core systems on a default management VLAN, with my user devices and guest devices on separate VLANs - e.g. so home users see Windows/Mac shares. but Guest users can see anything…

Bottom line - vSwitches needs a bit of spit and polish I think?