Re: [PATCH frr 1/2] frr: backport VXLAN local VTEP fallback fix

["Lukas Sichert" <l.sichert@proxmox.com>]

On 2026-07-14 13:18, Gabriel Goller <g.goller@proxmox.com> wrote:

> Backport the upstream fix for EVPN VXLAN interfaces without an explicit
> local IP address. Encode an unspecified VTEP as 0.0.0.0 so bgpd can fall
> back to the BGP router ID.
>
> Also include the upstream regression topotest.
>
> For more information also check the pve patch (optional):
> https://lore.proxmox.com/pve-devel/20260702143349.252142-1-g.goller@proxmox.com/
>
> Fixes: #7766
> Upstream: https://github.com/FRRouting/frr/pull/22555
> Signed-off-by: Gabriel Goller <g.goller@proxmox.com>

Tested on a three-node EVPN/VXLAN setup.

Without the patch, an address-less VXLAN interface caused bgpd to report:

  stream_get_ipaddr: unknown ip address-family: 0

and

Number of L2 VNIs: 0

With the patch, bgpd correctly registered the L2 VNI. Bidirectional
VXLAN traffic also worked with multiple local underlay addresses and
route-selected source addresses.

I have also tested this in combination with a pve-network patch, that
addresses the issue by setting vxlan-local-tunnelip explicitly [1]. This
also worked as expected [2].

Therefore consider this:

Tested-by: Lukas Sichert <l.sichert@proxmox.com>

[1] https://lore.proxmox.com/pve-devel/20260702143349.252142-1-g.goller@proxmox.com/
[2] https://lore.proxmox.com/pve-devel/DK3JYKQU39AH.34WYQGIZ0DIZR@proxmox.com/