On 12/17/25 10:31 AM, Dumitru Ceara wrote: > On 12/16/25 12:59 PM, Dumitru Ceara wrote: >> On 12/16/25 8:07 AM, Lorenzo Bianconi wrote: >>> Introduce the capability to specify the names used for EVPN devices: >>> - bridge device (default: br-$vni) >>> - vxlan device (default: vxlan-$vni) >>> - advertise device (default: lo-$vni) >>> >>> Reported-at: https://issues.redhat.com/browse/FDP-2730 >>> Signed-off-by: Lorenzo Bianconi <[email protected]> >>> --- >>> Changes since v1: >>> - Limit max device name size >>> - Add NEWS entry >>> - cosmetics in system-ovn.at >>> --- >> >> Hi Lorenzo, >> >> Thanks for this new revision! Applied to main. >> > > Hi Lorenzo, > > Unfortunately, when reviewing > https://patchwork.ozlabs.org/project/ovn/patch/13e7695cb8f0abdd20a6e39d6bc2bbbebb32fe17.1765899017.git.lorenzo.bianc...@redhat.com/ > I realized in this one we forgot about the dual stack case. > > I had mentioned it internally here: > https://issues.redhat.com/browse/FDP-2730?focusedId=28657789&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-28657789 > > But forgot to take that into account on the review. > > We need to be able to monitor two vxlan interfaces (one for IPv4 and one > for IPv6) for dual stack EVPN logical switches. > > The reason for that is that in Linux you cannot configure a single VXLAN > interface with multiple local IPs (one for v4 one for v6). > > So we need to change the new LS option from > "dynamic-routing-vxlan-ifname" to "dynamic-routing-vxlan-v4-ifname" and > "dynamic-routing-vxlan-v6-ifname". >
A small follow up, it might be cleaner to just turn dynamic-routing-vxlan-ifname into a list of vxlan interface names. Then the CMS can either: 1. not set dynamic-routing-vxlan-ifname -> vxlan-$vni is monitored (for AF_BRIDGE) by ovn-controller 2. set dynamic-routing-vxlan-ifname=vxlan-if1 -> vxlan-if1 is monitored (for AF_BRIDGE) by ovn-controller 3. set dynamic-routing-vxlan-ifname=vxlan-if1,vxlan-if2,..,vxlan-ifn -> vxlan-if1, vxlan-if2, ... vxlan-ifn are monitored (for AF_BRIDGE) by ovn-controller. "2" above is a special case of "3". That makes the implementation generic, allows dual-stack VXLAN underlays, and avoids new configuration knobs. > Would you be able to post a follow up patch? > > Thanks, > Dumitru > Regards, Dumitru _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
