VLAN in GUI

[mipsH]

Dear.

It will be a good choice to add a native support for VLANs in GUI for :

Linux native interfaces (LAN card, Bond, Bridge)

For now it is possible to use it, by manually modifying: /etc/network/interfaces, but it will be much better in GUI (with syntax check)

In OpenvSwitch it is implemented in OVS IntPort that can be inside VLAN, so it is mostly fine.




BR,
Hrvoje

 

[Chad Clarke]

Hrvoje,

Currently we have an interfaces template file that we use. After the initial install of a new PVE node, we copyp the interfaces template file to /etc/network/interfaces and update the IPs as need and it works great.

However, our team was discussing this the other day and also thought that it would be nice to have VLAN support built into the GUI as well as during the initial installation.

 

[manu]

Up to now we covered the most common use case, that the PVE bridge vmbr0 is connected to a switch where is receives the proper VLAN tags, and when creating a VM NIC you just need to specify one of those VLAN tags.

Can you please explain what is your use case in details ?

 

[mipsH]

Most of my usecases are:

ethxy cards ==> bond --> bridge ==> VLANs

For few years i was mostly use: OpenvSwitch Bond --> OVSbridge ==> OVS IntPort for every VLAN that i need (one OVS-Intport per VLAN ):

For example:

1. OVS IntPortVLAN100 - some with IP/Netmask/DG
2. OVS IntPortVLAN200 - some without IP, since you must have at least one OVSIntPort per VLAN to correctly bind it to VM/LXC network
3. OVS IntPortVLAN300 - some with IP/Netmask only - for STORAGE net for example
4. OVS IntPortVLANXY - some with IP/Netmask only - for CLUSTER/Web access etc net for example
   
5. ...

But if it will be much easy to create VLAN interface using GUI and Linux bond/bridge or on small servers deployments in which i can use dedicated eth port/card for few VLANs (in trunk mode) and later using VLAN interface, like:

• ethxy --> VLANxy bridge
  
• or
• ethx--> VLANx --> bridgeX
• ethy --> VLANy --> bridgeY

or any other possible case/combination in which we can have some VLAN (sub)interfaces.

So from my point of view it is not important on which layer we are dealing with VLANs until it is :

1. fast
2. reliable

In summary:

• In some cases you just need to propagate/trunk VLANs to the VM/LXC
• in another case you also need to have VLAN interfaces in addition like :
  • interface-VLAN-100 : IP, NETMASK, DefaultGateway - for Web Access, updates etc.
  • 
    
  • interface-VLAN-200 : IP, NETMASK - for Primary Storage Network (NAS/SAN)
  • interface-VLAN-201 : IP, NETMASK - for Backup Storage Network (NAS/SAN)
  • 
    
  • interface-VLAN-300 : IP, NETMASK - for Proxmox Cluster - ring0
  • interface-VLAN-301 : IP, NETMASK - for Proxmox Cluster - ring1
  • 
    
  • interface that is in trunk mode (vmbrXY), so you can propagate VLANs to VM/LXCs
• ... similar as explained in manual config : https://pve.proxmox.com/wiki/Vlans or https://pve.proxmox.com/wiki/Network_Model#Create_VLAN , but from GUI

In more details, scenarios :

For smallest deployment (one Proxmox VE + NAS storage for backup):

• One NIC (eth0):
  • VLAN 10 interface (maybe eth0.10) - with IP/Netmask/DG ,... --> For Web management
    
  • VLAN 20 interface (maaybe eth0.20) - with IP/Netmask --> For NAS backup Net
  • vmbr0 using eth0 - no IP - in trunk mode for all other VLANs (for example VLAN 30, 40) --> VLAN Aware for VM/LXCs

For larger deployments (2 or more NICs):

• eth0+eth1 = Bond0.100 or vmbr100 (with IP/Netmask,...) [VLAN100] - NAS storage Net
  
• eth0+eth1 = Bond0.200 or vmbr200 (with IP/Netmask/DG,...) [VLAN200] - Web mgmt and or Cluster net
  
• eth0+eth1 = Bond0 ==> vmbr0 (no IP - for VM/LXC) - trunk mode [TRUNK]
  
• or
• eth0+eth1 = Bond0 ==>VLAN-10-Interface--> vmbr10 (with IP/Netmask,...) [VLAN10]
  
• eth0+eth1 = Bond0 ==>VLAN-20-Interface--> vmbr20 (with IP/Netmask,DG...) [VLAN20]
  
• eth2+eth3 = Bond1 --> vmbr0 (no IP - for VM/LXC) - trunk mode [TRUNK] or in worst case like in OVSIntPort- one VLAN interface per OVSIntPort - for VMs/LXCs inside that VLAN
  
• and similar scenarios in which you can create VLAN interfaces on LAN card, Bond interface in bridge interface or bridge interaface to be VLAN aware (in trunk mode).

Br,
Hrvoje