Package: openvswitch-switch
Version: 3.5.0-1+b1
Severity: important
Tags: upstream fixed-upstream

Dear Maintainer,


STP/RSTP can incorrectly exclude OVS internal ports from flooding,
breaking IPv4 ARP and IPv6 neighbor discovery. 
Disabling STP/RSTP can leave the ports non-floodable. 
Existing learned unicast traffic may continue, while connectivity requiring 
neighbor discovery fails.

I reproduced this using Debian trixie's openvswitch source 3.5.0-1 on
amd64 with Linux 6.12.116+deb13-amd64. 
The isolated topology used a userspace netdev bridge, a veth peer and an 
internal TAP interface.
Tests started with empty neighbor caches and waited for participating ports to 
reach Forwarding state. 
Internal ports should remain floodable without participating in STP/RSTP.

Two upstream fixes address the problem:

1. Recompute bundle floodability after disabling STP/RSTP:
  
https://github.com/openvswitch/ovs/commit/332ca1dad732ce65375cc0b227cc1b118cab89f1

2. Check each port's STP/RSTP participation instead of the bridge setting:
  
https://github.com/openvswitch/ovs/commit/4a13c93a69b60b11a31bd315364eedab83fda581

Packet-test results were identical for STP and RSTP:

                   Initially disabled  Enabled  Disabled again
Unmodified                 PASS          FAIL        FAIL
Fix 1 only                 PASS          FAIL        PASS
Both fixes                 PASS          PASS        PASS

Each condition checked ARP replies, IPv4 neighbor resolution, and IPv4 and IPv6 
connectivity. 
Both fixes together also passed all four relevant upstream regression tests.

Could you consider applying the fixes where missing and back porting both to 
trixie?


Package: openvswitch-switch
Version: 3.5.0-1+b1

--
Hideaki Shimomura
[email protected]

Reply via email to