David Marchand <[email protected]> writes: > When a configuration change triggers an interface destruction/creation > (like for example, setting ofport_request), a port object may still be > referenced as a fport or a rport in the mdb. > > Before the fix, when flooding multicast traffic: > bridge("br0") > ------------- > 0. priority 32768 > NORMAL > -> forwarding to mcast group port > >> mcast flood port is unknown, dropping > -> mcast flood port is input port, dropping > -> forwarding to mcast flood port > > Before the fix, when flooding igmp report traffic: > bridge("br0") > ------------- > 0. priority 32768 > NORMAL > >> mcast port is unknown, dropping the report > -> forwarding report to mcast flagged port > -> mcast port is input port, dropping the Report > -> forwarding report to mcast flagged port > > Add relevant cleanup and update unit tests. > > Fixes: 4fbbf8624868 ("mcast-snooping: Flush ports mdb when VLAN configuration > changed.") > Signed-off-by: David Marchand <[email protected]> > --- > Changes since v1: > - updated the test on report flooding, >
Acked-by: Paolo Valerio <[email protected]> _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
