> Use auto...On Aug 17, 2022 18:02, topro <to...@gmx.de> wrote: Ok, now I sacrificed one of my affected hosts by migrating away any guests and putting it in a place where I got access to physical keeyboard and screen, so I have a playground for testing. I tried any combination of auto and/or allow-ovsbr1 I could imagine. The outcome is always the same.
I tested further and noticed that I do not need to do an actual update to break my network config but a simple "service openvswitch-switch restart" already is enough. To be more precise, when I do a "service openvswitch-switch stop", it won't touch my networking config. Only after subsequent "service openvswitch-switch start" all my configured interfaces are down. I do need auto on the bridge and [auto|allow ovsbr1] to have a working network after boot. But whatever I do, after openvswitch restart my interfaces are down. I also tried packages from stable-backports, no change. Yet, this config did work fine on older versions of openvswitch. Interrestingly enough there seems to be a related bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989720#41 featuring an interresting statement: "Yeah. FYI, I'm about to release 2.17.x in Debian. I'll make sure it closes this bug." Is there any chance I would need to wait for 2.17 to get that issue resolved? I'm sorry I cannot try with 2.17 packages from experimental as that has way too many dependencies to testing/sid packages. Now that I have a testground, is there anything you would like me to test in order to track down this issue? Best regards, topro
