openvswitch, last update?

[102020]

Greetings,

has anyone else had issues with OVS on the last update? I see it upgraded to 2.10.1. i had to change my bridges back to standard to even get gui access.
ovs-system shows DOWN state, vmbr1 shows UNKNOWN state. any help would be appreciated. usually with my config, rebooting and such everything comes up just fine.

 

[102020]

update, i'm going to say something went hay wire, my OVS routes are totally gone.

 

[102020]

update, something in the last kernel update stops openvswitch-switch from auto creating the routes.
adding auto vmbr1 does add the routes, however making any changes in the webgui removes this line from /etc/network/interfaces.

Using purely ifupdown2 (the ip address add) command, how can I manually add these routes in the interfaces file? post-up is not a thing unless I install net-tools, but rather not having net-tools and ethtool, kinda pointless?

 

[spirit]

update, something in the last kernel update stops openvswitch-switch from auto creating the routes.
adding auto vmbr1 does add the routes, however making any changes in the webgui removes this line from /etc/network/interfaces.

Using purely ifupdown2 (the ip address add) command, how can I manually add these routes in the interfaces file? post-up is not a thing unless I install net-tools, but rather not having net-tools and ethtool, kinda pointless?

Hi,

which version of ifupdown2 do you use ? (dpkg -l|grep ifupdown2)

can you post your /etc/network/interfaces ?

 

[102020]

Hi,

which version of ifupdown2 do you use ? (dpkg -l|grep ifupdown2)

can you post your /etc/network/interfaces ?

ifupdown2 2.0.1-1+pve4


For what it matters, I ditched OVS completely, I honestly can do what I need with pfSense and layer 2 rather than layer 3 and OVS

 

[spirit]

thanks for the report even if you don't use ovs anymore. we have detected a bug with ovs and ifupdown2 2.0.1, it should be fixed soon.

 

[mfed]

I think I might hit this incompatibility issue when after the update one of my hosts suddenly stopped configuring the IP addresses from the configuration file. I had to scratch my head a lot. My solution was to ditch ifupdown2 rather than ovs...

 

[spirit]

I think I might hit this incompatibility issue when after the update one of my hosts suddenly stopped configuring the IP addresses from the configuration file. I had to scratch my head a lot. My solution was to ditch ifupdown2 rather than ovs...

should be fixed soon. I have send patch to dev mailing list. (Anyway, currently, they are not advantage to use ifupdown2 + ovs, as you can't reload ovs configuration)