From: Gabriel Goller <g.goller@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH frr 2/2] bump to version 10.6.1-1+pve2
Date: Fri, 15 May 2026 17:23:57 +0200 [thread overview]
Message-ID: <20260515152400.726794-3-g.goller@proxmox.com> (raw)
In-Reply-To: <20260515152400.726794-1-g.goller@proxmox.com>
Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
---
debian/changelog | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index b246abfbe50e..ca8b8875b175 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+frr (10.6.1-1+pve2) trixie; urgency=medium
+
+ * fix leaked EVPN routes with wrong nexthop when ipv4 via ipv6 is used
+
+ -- Proxmox Support Team <support@proxmox.com> Fri, 15 May 2026 17:10:11 +0200
+
frr (10.6.1-1+pve1) trixie; urgency=medium
* update upstream source to 10.6.1
--
2.47.3
next prev parent reply other threads:[~2026-05-15 15:24 UTC|newest]
Thread overview: 6+ 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 ` Gabriel Goller [this message]
2026-05-16 23:59 ` [PATCH frr 0/2] Fix leaked EVPN routes having wrong nexthop on IPv4 via IPv6 routes Thomas Lamprecht
-- strict thread matches above, loose matches on Subject: below --
2026-05-15 9:14 [PATCH frr 0/2] Backport FRR EVPN local RT2 leaking fixes Gabriel Goller
2026-05-15 9:14 ` [PATCH frr 2/2] bump to version 10.6.1-1+pve2 Gabriel Goller
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=20260515152400.726794-3-g.goller@proxmox.com \
--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 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.