[PVE-User] VLANs

[Uwe Sauter]

Hi Dimitri,

Am 28.02.2017 um 19:51 schrieb Dimitri Alexandris:
> Since you know how to make a bond (switch + proxmox settings), you should
> learn and use Openvswitch:
> 
> https://pve.proxmox.com/wiki/Open_vSwitch
> 
> It's a faster and more elegant solution.  I use it exclusively now with
> every Proxmox i run.

Can you elaborate why OpenVSwitch is faster? Do you have benchmark numbers?

I'm currently in the process of migrate older infrastructure to a PVE cluster which runs a more complex version of my
previous example (bonds, VLANs and several separated uplinks). I personally have a little experience with OpenVSwitch
but I don't know if it is worth the struggle to teach my colleagues. They only know about "the good ol' times" (tm).

Regards,

	Uwe

> 1-  Install it via console:  apt install openvswitch-switch .
> 
> 2-  From Proxmox GUI, delete all of your present configutation.  Keep a
> backup first of your existing /etc/network/interfaces  just in case.
> 
> 3-  Create an OVS Bond, with vmbr0 and both your ethernets as members.  I
> use [LACP (balance-slb)].  If you don't see a vmbr available, create this
> first (OVS Bridge) with another eth, and later you remove the eth from it.
> 
> 4-  Don't assign an IP on vmbr0.
> 
> 5-  Add as many OVS IntPorts you need, each with it's own VLAN and
> optionally an IP and/or GW.  You should see bond0, lan, dmz, etc. as vmbr0
> members.
> 
> 6-  Configure your switch (both ports AND bond) to your VLANS, all tagged.
> 
> 7-  Reboot.
> 
> In your Network settings page, you should see only OVS elements (+ the two
> eths of the bond as Network Devices).
> 
> You can assign IPs directly to vmbrs when you don't need other VLANs on
> them.
> 
> 
> 
> On Tue, Feb 28, 2017 at 6:36 PM, Uwe Sauter <uwe.sauter.de at gmail.com> wrote:
> 
>> I have a setup where I don't use Proxmox own VLAN management but have one
>> bridge per VLAN that I use:
>>
>> /etc/network/interfaces
>> ###
>> auto lo
>> iface lo inet loopback
>>
>> auto eth0
>> iface eth0 inet static
>>         address 192.168.253.200
>>         netmask 255.255.255.0
>>         gateway 192.168.253.254
>>
>> auto eth0.101
>> iface eth0.101 inet manual
>>
>> auto eth0.102
>> iface eth0.102 inet manual
>>
>> auto vmbr101
>> iface vmbr101 inet manual
>>         bridge_ports eth0.101
>>         bridge_stp off
>>         bridge_fd 0
>>
>> auto vmbr102
>> iface vmbr102 inet manual
>>         bridge_ports eth0.102
>>         bridge_stp off
>>         bridge_fd 0
>>
>> ###
>>
>> eth0 is used for access to the Proxmox host.
>> VLAN 101 and 102 are used for VMs.
>> Ths switch port is configured for VLAN 100 untagged (native) and VLAN 101
>> and 102 tagged.
>>
>> This gives you two VLANs that can be assigned separately to you VMs.
>>
>> If you need more details, keep asking.
>>
>>
>> Regards,
>>
>>         Uwe
>>
>> Am 28.02.2017 um 16:32 schrieb Daniel:
>>> Hi there,
>>>
>>> i wanted to create a VLAN based on my Bonding interface.
>>> I was looking in  the wiki (https://pve.proxmox.com/wiki/Category:HOWTO)
>> but I didn’t find any ideas. Just old Versions seems to be documented.
>>>
>>> Could you tell me who I can setup an VLAN without an IP Assigned to that
>> interface and how can I add this later on a Container/VM.
>>> Just change vmbr0 interface to the VLAN interface?
>>>
>>> --
>>> Grüsse
>>>
>>> Daniel
>>> _______________________________________________
>>> pve-user mailing list
>>> pve-user at pve.proxmox.com
>>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>>
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>