On 3/22/23 10:42, Eelco Chaudron via discuss wrote: > > > On 21 Mar 2023, at 23:42, Alex Zetaeffesse via discuss wrote: > >> Hi all, >> >> First of all, let me be clear on the fact that I'm the first who doesn't >> want to run a mixed environment :-) >> >> In my ProxMox environment I have the following: >> >> root@pve:~# ip link show dev vmbr1 >> 11: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state >> UNKNOWN mode DEFAULT group default qlen 1000 >> link/ether 00:1c:c4:47:63:31 brd ff:ff:ff:ff:ff:ff > > This is the same on my Fedora and RHEL systems. The bridge show DOWN if I > bring it down, and UNKNOWN state when it’s up. > > [vagrant@f35 ~]$ sudo ovs-vsctl add-br br1 > [vagrant@f35 ~]$ ip link show bro > 6: br1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT > group default qlen 1000 > link/ether c6:c4:18:57:ba:48 brd ff:ff:ff:ff:ff:ff > [vagrant@f35 ~]$ sudo ip link set br1 up > [vagrant@f35 ~]$ ip link show br1 > 6: br1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state > UNKNOWN mode DEFAULT group default qlen 1000 > link/ether c6:c4:18:57:ba:48 brd ff:ff:ff:ff:ff:ff > > This might be a bug no one ever noticed :)
IF_OPER_UNKNOWN (0): Interface is in unknown state, neither driver nor userspace has set operational state. Interface must be considered for user data as setting operational state has not been implemented in every driver. I'm guessing that the latter applies to the OVS internal port, i.e. we probably do not set operational state for them in the kernel. But that should not affect the traffic in any way as the kernel should treat the UNKNOWN state more or less the same way as UP. Best regards, Ilya Maximets. _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
