well, vlan support exist since kernel 3.8, so 2013*lately* Linux Brdiges have better VLAN 802.1q tagging support, but that wasn't the case long time ago, with only OpenVSwitch being the "real" alternative for vlans and trunking in the same virtual switch.
yes me too But ovs is not old too (~ 2010) if you compare about the vlan feature.For somebody that have worked on/with Linux since kernel 0.92 and used bridge since ~2000, 3.8 is quite "new"
just enable vlan-aware option on bridge ?I have been thinking about moving from Linux Bridges to OVS. The reason that I wanted to move to OVS is that I have decided that I wanted to virtualize pfSense and I make use of about 12 VLANs and it seems to easier to work with VLANS under OVS as Linux bridges. Also since I am using PM with a single interface (laptop), I have even more need of VLANs.
So would I still have to create entries in /etc/network/interface file? For instance, I am pretty clear that I need to create an interface for pfsense VMBR1 [WAN] VMBR2 [LAN] and VMBR3 [OPT]), so I would create that in /etc/network/interface. Now under pfSense, I create VLAN 5, 10, 20 30 40, etc under the OPT interface., do I need to added entries in the /etc/network/interface or would I be good to go just worrying about creating VLANs only in pfSense.by default, linux bridge don't support vlan.
if you enable the option "vlan aware" , in the gui "host->system->network->youbridge options,
the bridge will transport the vlans.(like OVS) (and than you can create vlan interfaces in your pfsense)
still younger than OVS's vlanyes me too But ovs is not old too (~ 2010) if you compare about the vlan feature.
If the OOM kicked in, then you are screwed on the Hypervisor in anycase. The OOM is well.... let's say I have a preference for proper OS's like Solaris and not debate that part.Personally, I still prefer linux bridge than ovs. (if ovs deamon is killed or oom, you don't have network anymore :/ . and I have see a lot of bug report recently with packet drop and strange stack traces)
So, yes the typical would be something like:I have been thinking about moving from Linux Bridges to OVS. The reason that I wanted to move to OVS is that I have decided that I wanted to virtualize pfSense and I make use of about 12 VLANs and it seems to easier to work with VLANS under OVS as Linux bridges. Also since I am using PM with a single interface (laptop), I have even more need of VLANs.
Seems with the "new improved" Linux Bridge, that is not needed anymore...The regular bridge mode (I'm probably reading old tutorials and forum posts) seemed to require that every vlan get explicitly defined on a port
The only things I've been putting in the "OVS options" field is things likeNow that I have OVS installed on new nodes I'm just seeing a new field "OVS options"...I was hoping for some GUI implementation that would let you list the vlans and make one a native vlan if required.
I've been looking for an ideal tutorial of some sort using proxmox, OVS and ceph. Any recommendations?
Tagfield, and to make it trunk, you'll need to add a
vlan_mode, else a tagged interface is an access interface (mapped to the Vlan)