From: Hannes Laimer <h.laimer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs/manager/network 0/6] add SLAAC support for subnets in EVPN zones
Date: Wed, 18 Feb 2026 11:23:44 +0100 [thread overview]
Message-ID: <20260218102350.211294-1-h.laimer@proxmox.com> (raw)
Rather than just enabling SLAAC, this allows configuring/enabling RAs.
So SLAAC support is rather a consequence of being able to configure RAs.
The second patch for `pve-network` contains some context from why we set
`accept_untracked_na=2`.
This also adds a new example setup to the sdn docs, specifically how to
setup a evpn zone with an openfabric underlay and two ipv6 subnets. One
with SLAAC and one with static v6 addresses. The second one is a `/96`
and should show how to configure smaller than `/64` GUA prefixes without
SLAAC.
pve-network:
Hannes Laimer (3):
sdn: evpn: add ipv6-nd support for subnets
sdn: evpn: accept untracked IPv6 NA on EVPN vnet bridges
api: vnet: include zone-type in vnet list
src/PVE/API2/Network/SDN/Subnets.pm | 8 +++
src/PVE/API2/Network/SDN/Vnets.pm | 13 ++++
src/PVE/Network/SDN/Controllers/EvpnPlugin.pm | 42 ++++++++++-
src/PVE/Network/SDN/SubnetPlugin.pm | 70 +++++++++++++++++++
src/PVE/Network/SDN/Zones/EvpnPlugin.pm | 14 +++-
.../exitnode_snat/expected_sdn_interfaces | 1 +
.../exitnodenullroute/expected_sdn_interfaces | 1 +
.../evpn/ipv4ipv6/expected_sdn_interfaces | 1 +
.../ipv4ipv6nogateway/expected_sdn_interfaces | 1 +
.../zones/evpn/ipv6/expected_sdn_interfaces | 1 +
.../evpn/ipv6underlay/expected_sdn_interfaces | 1 +
11 files changed, 151 insertions(+), 2 deletions(-)
pve-manager:
Hannes Laimer (1):
ui: sdn: add ipv6 options for subnets in evpns zones
www/manager6/form/SDNVnetSelector.js | 2 +-
www/manager6/sdn/SubnetEdit.js | 132 ++++++++++++++++++++++++++-
www/manager6/sdn/SubnetView.js | 6 +-
www/manager6/sdn/VnetView.js | 5 +-
4 files changed, 140 insertions(+), 5 deletions(-)
pve-docs:
Hannes Laimer (2):
sdn: add subnet ipv6 options section
sdn: add exmaple for ipv6 in an evpn zone
pvesdn.adoc | 240 ++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 240 insertions(+)
Summary over all repositories:
16 files changed, 531 insertions(+), 7 deletions(-)
--
Generated by murpp 0.9.0
next reply other threads:[~2026-02-18 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 10:23 Hannes Laimer [this message]
2026-02-18 10:23 ` [PATCH pve-network 1/3] sdn: evpn: add ipv6-nd support for subnets Hannes Laimer
2026-02-18 10:23 ` [PATCH pve-network 2/3] sdn: evpn: accept untracked IPv6 NA on EVPN vnet bridges Hannes Laimer
2026-02-18 10:23 ` [PATCH pve-network 3/3] api: vnet: include zone-type in vnet list Hannes Laimer
2026-02-18 10:23 ` [PATCH pve-manager 1/1] ui: sdn: add ipv6 options for subnets in evpns zones Hannes Laimer
2026-02-18 10:23 ` [PATCH pve-docs 1/2] sdn: add subnet ipv6 options section Hannes Laimer
2026-02-18 10:23 ` [PATCH pve-docs 2/2] sdn: add exmaple for ipv6 in an evpn zone Hannes Laimer
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=20260218102350.211294-1-h.laimer@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 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.