Hi, sorry for html mail (my fault), here again in plain text format... as I am affected by exactly the described behaviour with exactly the mentioned version of openvswitch packages, I gave the workaround proposed in message #10 a try. For me it did not fix the behavior. As my affected host is headless I cannot easily determine the state after network is left behind in a broken way. As I do apt upgrade over network I run it inside a screen session. Up until today output stopped when network link got broken like this: Setting up openvswitch-common (2.15.0+ds1-2+deb11u1) ... Setting up openvswitch-switch (2.15.0+ds1-2+deb11u1) ...
Saving flows. Exiting ovsdb-server (1220). Starting ovsdb-server. Configuring Open vSwitch system IDs. Exiting ovs-vswitchd (1235). Starting ovs-vswitchd. Now for the very first time I got three more lines before connection broke: ovs-ofctl: ovsbr1 is not a bridge or a socket ovs-ofctl: ovsbr1 is not a bridge or a socket ovs-ofctl: ovsbr1 is not a bridge or a socket My network configuration file looks like this auto lo iface lo inet loopback auto ovsbr1 iface ovsbr1 inet manual ovs_type OVSBridge ovs_ports eth0 ovsvlan99 # eth0 onboard hw ethernet device allow-ovsbr1 eth0 iface eth0 inet manual ovs_type OVSPort ovs_bridge ovsbr1 up ip link set dev $IFACE up down ip link set dev $IFACE down # ovsvlan99 internal network device through openvswitch allow-ovsbr1 ovsvlan99 iface ovsvlan99 inet static address 192.168.99.80 netmask 255.255.255.0 gateway 192.168.99.1 ovs_type OVSIntPort ovs_bridge ovsbr1 ovs_options tag=99 Best regards, topro
