From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Hannes Laimer <h.laimer@proxmox.com>
Subject: Re: [PATCH network v2 0/4] sdn: evpn: IPv6 underlay support
Date: Mon, 18 May 2026 12:20:38 +0200 [thread overview]
Message-ID: <177909919143.3110381.3763965075645409286.b4-ty@b4> (raw)
In-Reply-To: <20260515110648.217493-1-h.laimer@proxmox.com>
On Fri, 15 May 2026 13:06:44 +0200, Hannes Laimer wrote:
> After we bumped frr this will work now, so rebased it and sent it again. Adds
> IPv6 underlay support for EVPN: IPv6-capable underlays can be selected and IPv6
> peers configured. On a dual-stack underlay the EVPN session picks IPv6.
>
> I mostly tested this on top of the bgp-fabric series[2], but it does not depend
> on the changes in the that series.
>
> [...]
Applied, thanks!
[1/4] sdn: evpn: prepare IPv6 underlay support
commit: fbf93d81818645406fcbadba7723e57b1a5858fc
[2/4] sdn: evpn: keep router-id valid on IPv6 underlay
commit: fa20a4091a92e62236d6462ead2e03423e70eb6b
[3/4] sdn: stabilize peer IP ordering when generating sdn config
commit: a22cf9eeeb529c3eb4821e710e237bd6516ded7e
[4/4] sdn: evpn: add tests covering ipv6 underlays
commit: 0e99f82b30c63c1bd8c305dbd7006c3c8af2febf
prev parent reply other threads:[~2026-05-18 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 11:06 [PATCH network v2 0/4] sdn: evpn: IPv6 underlay support Hannes Laimer
2026-05-15 11:06 ` [PATCH pve-network v2 1/4] sdn: evpn: prepare " Hannes Laimer
2026-05-15 11:06 ` [PATCH pve-network v2 2/4] sdn: evpn: keep router-id valid on IPv6 underlay Hannes Laimer
2026-05-15 11:06 ` [PATCH pve-network v2 3/4] sdn: stabilize peer IP ordering when generating sdn config Hannes Laimer
2026-05-15 11:06 ` [PATCH pve-network v2 4/4] sdn: evpn: add tests covering ipv6 underlays Hannes Laimer
2026-05-18 10:20 ` 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=177909919143.3110381.3763965075645409286.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=h.laimer@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