public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Hannes Laimer <h.laimer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: superseded: [pve-devel] [PATCH network 0/6] add EVPN IPv6 underlay support
Date: Fri, 15 May 2026 13:08:32 +0200	[thread overview]
Message-ID: <13e8b0a7-5a85-46d7-a06f-4890a5eebe2b@proxmox.com> (raw)
In-Reply-To: <20260122135151.292794-1-h.laimer@proxmox.com>

superseded-by:
https://lore.proxmox.com/pve-devel/20260515110648.217493-1-h.laimer@proxmox.com/

On 2026-01-22 14:51, Hannes Laimer wrote:
> This adds basic IPv6 underlay support for EVPN zones.
> This does rely on [1], without it FRR won't advertise v6 next-hops. So
> this should not be applied before the FRR version we ship includes [1],
> based on @Gabriel's estimate this could be included in a version that may
> be released early next month(february). I did test this with the latest
> master of FRR.
> 
> (this also needs the changes to `get_local_route_ip` added with [2])
> 
> Aside from that, like for VXLAN, we prefer IPv6 if the underlaying
> fabric should offer both, and we don't support peer addresses with
> different IP versions. So either all v6 or all v4.
> 
> 
> [1] https://github.com/FRRouting/frr/pull/19498
> [2] https://lore.proxmox.com/pve-devel/20260116110843.89615-2-h.laimer@proxmox.com/T/#u
> 
> pve-network:
> 
> Hannes Laimer (6):
>   sdn: evpn: prepare IPv6 underlay support
>   sdn: controller: fallback to interface mac if no master
>   sdn: controller: prevent invalid router-id generation from zero mac
>   sdn: evpn: keep router-id valid on IPv6 underlay
>   sdn: vxlan: sort peer IPs when generating sdn config
>   sdn: evpn: add tests covering ipv6 underlays
> 
>  src/PVE/Network/SDN/Controllers/EvpnPlugin.pm | 70 ++++++++++++---
>  src/PVE/Network/SDN/Controllers/Plugin.pm     |  9 +-
>  src/PVE/Network/SDN/Zones/EvpnPlugin.pm       | 28 ++++--
>  src/PVE/Network/SDN/Zones/VxlanPlugin.pm      |  2 +-
>  .../expected_controller_config                | 64 ++++++++++++++
>  .../expected_sdn_interfaces                   | 56 ++++++++++++
>  .../exitnode_local_routing_ipv6/interfaces    |  7 ++
>  .../exitnode_local_routing_ipv6/sdn_config    | 27 ++++++
>  .../expected_controller_config                | 86 +++++++++++++++++++
>  .../expected_sdn_interfaces                   | 64 ++++++++++++++
>  .../evpn/openfabric_fabric_ipv6/interfaces    |  6 ++
>  .../evpn/openfabric_fabric_ipv6/sdn_config    | 83 ++++++++++++++++++
>  .../expected_controller_config                | 74 ++++++++++++++++
>  .../expected_sdn_interfaces                   | 58 +++++++++++++
>  .../openfabric_fabric_ipv6_only/interfaces    |  6 ++
>  .../openfabric_fabric_ipv6_only/sdn_config    | 79 +++++++++++++++++
>  16 files changed, 701 insertions(+), 18 deletions(-)
>  create mode 100644 src/test/zones/evpn/exitnode_local_routing_ipv6/expected_controller_config
>  create mode 100644 src/test/zones/evpn/exitnode_local_routing_ipv6/expected_sdn_interfaces
>  create mode 100644 src/test/zones/evpn/exitnode_local_routing_ipv6/interfaces
>  create mode 100644 src/test/zones/evpn/exitnode_local_routing_ipv6/sdn_config
>  create mode 100644 src/test/zones/evpn/openfabric_fabric_ipv6/expected_controller_config
>  create mode 100644 src/test/zones/evpn/openfabric_fabric_ipv6/expected_sdn_interfaces
>  create mode 100644 src/test/zones/evpn/openfabric_fabric_ipv6/interfaces
>  create mode 100644 src/test/zones/evpn/openfabric_fabric_ipv6/sdn_config
>  create mode 100644 src/test/zones/evpn/openfabric_fabric_ipv6_only/expected_controller_config
>  create mode 100644 src/test/zones/evpn/openfabric_fabric_ipv6_only/expected_sdn_interfaces
>  create mode 100644 src/test/zones/evpn/openfabric_fabric_ipv6_only/interfaces
>  create mode 100644 src/test/zones/evpn/openfabric_fabric_ipv6_only/sdn_config
> 
> 
> Summary over all repositories:
>   16 files changed, 701 insertions(+), 18 deletions(-)
> 





      parent reply	other threads:[~2026-05-15 11:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 13:51 [pve-devel] [PATCH network 0/6] add EVPN IPv6 underlay support Hannes Laimer
2026-01-22 13:51 ` [pve-devel] [PATCH pve-network 1/6] sdn: evpn: prepare " Hannes Laimer
2026-01-22 13:51 ` [pve-devel] [PATCH pve-network 2/6] sdn: controller: fallback to interface mac if no master Hannes Laimer
2026-01-22 13:51 ` [pve-devel] [PATCH pve-network 3/6] sdn: controller: prevent invalid router-id generation from zero mac Hannes Laimer
2026-01-22 13:51 ` [pve-devel] [PATCH pve-network 4/6] sdn: evpn: keep router-id valid on IPv6 underlay Hannes Laimer
2026-01-22 13:51 ` [pve-devel] [PATCH pve-network 5/6] sdn: vxlan: sort peer IPs when generating sdn config Hannes Laimer
2026-01-22 13:51 ` [pve-devel] [PATCH pve-network 6/6] sdn: evpn: add tests covering ipv6 underlays Hannes Laimer
2026-05-15 11:08 ` Hannes Laimer [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=13e8b0a7-5a85-46d7-a06f-4890a5eebe2b@proxmox.com \
    --to=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal