From: Gabriel Goller <g.goller@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH frr 1/2] frr: backport #21166 and #21958, fixing EVPN IPv4 routes with IPv6 nexhtop
Date: Fri, 15 May 2026 18:06:39 +0200 [thread overview]
Message-ID: <l3lhoec3rcufxpjd7bbfslin7epshccltldlhs5eepp3nkxp7h@ibgyy6fhktjz> (raw)
In-Reply-To: <20260515152400.726794-2-g.goller@proxmox.com>
On 15.05.2026 17:23, Gabriel Goller wrote:
> When leaking EVPN routes with a IPv4 prefix and a IPv6 nexthop (e.g. on
> IPv6 VTEPs), then the routes in the destination VRF have a nexthop of
> 0.0.0.0. This is because the EVPN AF in bgpd sets the BGP_ATTR_NEXT_HOP
> flag, which means only the bgp next-hop property is checked and not the
> bgp MP (multiprotocol, bgp4) next-hop (which is the one that contains
> the ipv6 addr). So bgpd just makes up a ipv4 address and sends it to
> ipv4. Some changes have been done in a previous commit, but this
s/ipv4/zebra/
-_-
> particular issue hasn't been fixed, so upstreamed the change.
>
> [1]: https://github.com/FRRouting/frr/pull/21166
> [2]: https://github.com/FRRouting/frr/pull/21958
>
> Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
> [snip]
next prev parent reply other threads:[~2026-05-15 16:06 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 [this message]
2026-05-15 15:23 ` [PATCH frr 2/2] bump to version 10.6.1-1+pve2 Gabriel Goller
2026-05-16 23:59 ` [PATCH frr 0/2] Fix leaked EVPN routes having wrong nexthop on IPv4 via IPv6 routes Thomas Lamprecht
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=l3lhoec3rcufxpjd7bbfslin7epshccltldlhs5eepp3nkxp7h@ibgyy6fhktjz \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox