I previously asked this question about Bridge networks here.
My situation is that I want a VM to be connected to multiple network interfaces at once. One of these networks will advertise itself as the default route, and the other network will be used for traffic destined for its own specific subnet.
Unlike Bridge, there is no raw.dnsmasq option for me to override the router advertisements.
Yeah, I don’t think there’s anything that allows for that now short of messing directly with the OVN config which could backfire when Incus decides to make an update.
On the IPv4 side we have ipv4.dhcp.gateway=none for this now, but there’s no real analog for IPv6 as DHCPv6 specifically does not advertise routes and SLAAC can only announce itself as a route.
Maybe we can introduce an ipv6.slaac.gateway=false to control that, assuming OVN has the rights knobs for it.
I see. In OVN networks, OVN controls DHCP and Router Advertisements?
I thought Open vSwitch was primarily concerned with ACLs, not host management.
Yeah, when using OVN networking everything turns into flow rules which get pushed down to OVS. There is no DHCP, SLAAC or DNS daemon anywhere when using OVN, what looks like a DHCP, DNS or SLAAC response is nothing more than pre-defined flow rules that trigger a response be sent to the client on match.
From looking at the docs, there doesn’t seem like there’s a way to advertise a default lifetime of 0. But there is an option for configuring router priority.