From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Gabriel Goller <g.goller@proxmox.com>
Subject: Re: [PATCH frr 0/2] Fix leaked EVPN routes having wrong nexthop on IPv4 via IPv6 routes
Date: Sun, 17 May 2026 01:59:44 +0200 [thread overview]
Message-ID: <177897588452.770468.5372557993508508653.b4-ty@b4> (raw)
In-Reply-To: <20260515152400.726794-1-g.goller@proxmox.com>
On Fri, 15 May 2026 17:23:55 +0200, Gabriel Goller wrote:
> When we have a EVPN fabric with IPv6 VTEPs and leak them into the default
> routing table (or any other VRF) (via exit-nodes in our case) the nexthop is
> wrong. The nexthop is correct in the vrf (e.g. `ip route show vrf vrf_evpn`) but
> the import-vrf does not correctly check the BGP MP properties for the IPv6
> nexthop and inserts a invalid (0.0.0.0) IPv4 nexthop. The BGP MP properties are
> not checked because a legacy bgp flag is set (BGP_ATTR_NEXT_HOP), which
> circumvents the BGP MP check.
>
> [...]
Smoke-Tested in a peer-to-peer EVPN setup over an IPv6 underlay: a type-3 route
from a v6 VTEP propagates to the peer with the v6 nexthop preserved, looked all
ok and improves the stats quo, so after some longer consideration:
Applied, thanks!
[1/2] frr: backport #21166 and #21958, fixing EVPN IPv4 routes with IPv6 nexhtop
commit: 1e04e21152138c90ba9c612707a95c5fb48cf9d6
[2/2] bump to version 10.6.1-1+pve2
commit: 9f188e1b4459edfd6174aa1ad48ee4ab6bde7749
prev parent reply other threads:[~2026-05-17 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 15:23 [PATCH frr 0/2] Fix leaked EVPN routes having wrong nexthop on IPv4 via IPv6 routes Gabriel Goller
2026-05-15 15:23 ` [PATCH frr 1/2] frr: backport #21166 and #21958, fixing EVPN IPv4 routes with IPv6 nexhtop Gabriel Goller
2026-05-15 16:06 ` Gabriel Goller
2026-05-15 15:23 ` [PATCH frr 2/2] bump to version 10.6.1-1+pve2 Gabriel Goller
2026-05-16 23:59 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177897588452.770468.5372557993508508653.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=g.goller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.