setup ovs bridges from webgui

[immo]

HI,

I use proxmox 4.4

if I create a ovs bridge the gui creates the interfaces part automatically and I can see the is just

+auto vmbr251
+iface vmbr251 inet manual
+ ovs_type OVSBridge
+ ovs_ports eth1

but your documentation says
https://pve.proxmox.com/wiki/Open_vSwitch#Bridges

...
However, any interfaces (Physical, OVSBonds, or OVSIntPorts) associated with a bridge should have their definitions prefixed with allow-$brname $iface, e.g. allow-vmbr0 bond0
...​

whats the correct way ? gui or documentation ?

 

[dietmar]

whats the correct way ? gui or documentation ?

We usually do the correct setup (Did you run into any problems?)

 

[immo]

I just do see a difference between docu and gui process....
And my support engineer told me he created all manually and never via GUI. So may be nobody knows...

this seems to be a working setup:

auto vmbr250
allow-ovs vmbr250
iface vmbr250 inet manual
ovs_type OVSBridge
ovs_ports eth3.250
post-up ifconfig vmbr250 up
mtu 9000

auto eth3.250
allow-vmbr250 eth3.250
iface eth3.250 inet manual
ovs_bridge vmbr250
ovs_type OVSPort​

BUT from now I get a GUI Error
interface 'eth3.250' is not defined as OVS port/bond (500)
if I try to create a further one.
But it is defined as OVS port

 

[Richard]

I just do see a difference between docu and gui process....
And my support engineer told me he created all manually and never via GUI. So may be nobody knows...

this seems to be a working setup:

auto vmbr250
allow-ovs vmbr250
iface vmbr250 inet manual
ovs_type OVSBridge
ovs_ports eth3.250
post-up ifconfig vmbr250 up
mtu 9000

auto eth3.250
allow-vmbr250 eth3.250
iface eth3.250 inet manual
ovs_bridge vmbr250
ovs_type OVSPort​

BUT from now I get a GUI Error
interface 'eth3.250' is not defined as OVS port/bond (500)
if I try to create a further one.
But it is defined as OVS port

The above will not work - define OVS bridges as well as internal ports with VLAN tags by GUI (the created /etc/network/interfaces[.new] will show you the correct syntax).

The allow-vmbr.. statement is correct and always generated by GUI too - maybe there was a misunderstanding when interpreting the diff-file.

 

[tonnic]

old thread but when I create my OVS Bridge in GUI, it doesn't have "allow-vmbr ", but rather "auto" like the OP says.

 

[spirit]

old thread but when I create my OVS Bridge in GUI, it doesn't have "allow-vmbr ", but rather "auto" like the OP says.

if you have installed ifupdown2, it's used "auto" instead "allow-vmbr"