Feature request: expose OVN multicast (IGMP snooping) config on ovn network type

Hey everyone! At the lab I’m working in right now, we’re currently using Incus and OVN to power our baremetal infrastructure. However, we do intend to do a lot of multicasting, so I wanted to propose this feature so that Incus may configure it for OVN.

Core OVN supports IP multicast via IGMP snooping (other_config:mcast_snoop) and IGMP relay across logical routers (options:mcast_relay). Right now, the Incus ovn network type doesn’t expose either setting. The only supported config namespaces are bridge, dns, ipv4, ipv6, security, and user.

To test multicast today, I have to manually run ovn-nbctl set Logical_Switch other_config:mcast_snoop=true directly against the Northbound DB, bypassing Incus entirely. This isn’t reliable since any network reconciliation by Incus can reset the setting.

Request: add a config key such as ovn.mcast_snoop (bool) on the ovn network type, and ideally ovn.mcast_relay for routing multicast between logical switches via a logical router. This would let multicast-dependent workloads (streaming, clustering protocols, service discovery) run natively on OVN-backed networks without manual OVN DB edits.

Happy to test against a dev build if this is picked up.

We do have bridge.multicast_snooping in the bridged network driver, so I think it would make sense to align naming and behavior here.

So basically:

  • Add bridge.multicast_snooping to OVN and have it follow the same behavior (on by default)
  • Add bridge.multicast_relay to OVN with it defaulting to off