[SOLVED] Proxmox 6.1: ifupdown2 not working with Open vSwitch

[dksoft]

I just installed 6.1 and ifupdown2 because the release notes promised that networking can be restartet after changes without reboot.

Is it a known problem that the same configuration on Open vSwitch does not work if ifupdown2 is installed?

Removing ifupdown2 makes the system working again.


Thanks,
dksoft

Just in case my interfaces:

auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet manual

iface eno3 inet manual

iface eno4 inet manual

iface enp1 inet manual

allow-vmbr0 enp1
iface enp1 inet manual
    ovs_type OVSPort
    ovs_bridge vmbr0
    up sysctl -w net.ipv6.conf.$IFACE.disable_ipv6=1

auto lan
allow-vmbr0 lan
iface lan inet static
    ovs_type OVSIntPort
    ovs_bridge vmbr0
    address 10.0.0.8
    netmask 255.255.255.0
    gateway 10.0.0.1
    dns-nameservers 10.0.0.1
    dns-domain intra

iface lan inet6 auto
    address fd00::8
    netmask 64
    dns-nameservers fd00::1
    dns-domain intra
    up ip token set ::8 dev $IFACE

auto vmbr0
iface vmbr0 inet manual
    ovs_type OVSBridge
    ovs_ports enp1 lan
    up sysctl -w net.ipv6.conf.$IFACE.disable_ipv6=1
# LAN

 

[Alwin]

I just installed 6.1 and ifupdown2 because the release notes promised that networking can be restartet after changes without reboot.

Is it a known problem that the same configuration on Open vSwitch does not work if ifupdown2 is installed?

Removing ifupdown2 makes the system working again.

Yes it can. With the exception, of ifreload not being compatible with openvswitch at the moment.

EDIT: As a workaround you can restart the networking service.

 

[dksoft]

Thanks for taking care of this, Alwin.

Yes, restarting the networking fixes the problem. In this case I also must restart the VMs.
Do I understand correctly, that it is better to not use ifupdown2 with openvswitch in the moment?

 

[tom]

Read admin docs on https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_network_configuration

(ifupdown2 cannot understand OpenVSwitch syntax, so reloading is not possible if OVS interfaces are configured.)

 

[wolfgang]

openvswitch in the moment?

Is there a reason why you need Open vSwitch?
As far you ask me there are only two real reasons to use it.
1.) you need mirror ports.
2.) you need Open-Flow.

 

[Catwoolfii]

As far you ask me there are only two real reasons to use it.
1.) you need mirror ports.
2.) you need Open-Flow.

what about ovs inport?

 

[wolfgang]

what about ovs inport?

Do you mean intport or inport?
The intport is a vdev that exists in the Linux network model too.

 

[spirit]

Hi,

you should replace
auto vmbr0
by
allow-ovs vmbr0


(proxmox 6.1 already change that if you edit config with gui)

like this, they are no conflict with ifupdown2

 

[dksoft]

Is there a reason why you need Open vSwitch?

Because it works like a hardware switch does.

E.g. I have one bridge which is connected as a VLAN trunk port to my network and the VMs use their own VLANs on that bridge.
This includes 802.1q, e.g. VLAN in VLAN.

On Linux bridge multiple VLANs are more complex. I experienced that the PVE GUI breaks the configuration when you have multiple VLAN tagged devices and bridges. It's complex to find the right notation of /etc/network/interfaces that the GUI unterstands.

Also I did not make IPv6 working reliable on Linux bridge (see my other posting).

So far my problem is solved by not using ifupdown2.