public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Lukas Sichert" <l.sichert@proxmox.com>
To: "Hannes Laimer" <h.laimer@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH docs/manager/network/proxmox{-perl-rs,-ve-rs} v5 0/9] add IPv6 RA / SLAAC support to EVPN zones
Date: Mon, 02 Nov 2026 15:25:52 +0100	[thread overview]
Message-ID: <DMKSM1CTXTLF.ENLD69OZ1NO5@proxmox.com> (raw)
In-Reply-To: <20261029154148.2882594-1-h.laimer@proxmox.com>

On 2026-10-29 16:41, Hannes Laimer <h.laimer@proxmox.com> wrote:

> This series adds IPv6 Router Advertisement / SLAAC support to EVPN
> zones.

I have tested this by setting up a new EVPN Zone and enabling it on an
existing EVPN zone. Inside of the EVPN zone I used the installer of an
ubuntu server 26.04 to test configuration without any prior
configuration. This worked correctly and the new address was inside the
subnet. Also with tcpdump I was able to verify that the Managed and
Other flag were sent correctly. Also RDNSS was correctly advertised to
the machine when set. Inside the Subnet pane the SLAAC A option could
be used to disable SLAAC for that subnet. I did not test the L flag nor
the advanced options, as those are hidden even with "Advanced" ticked.
As far as I can tell from a quick glance into proxmox-widget-toolkit it
would need to be fixed there, because the advanced button only toggles
the advanced options for the general pane. Alternatively, all of the
options could be made non-advanced.

Two minor observations, which I would not consider necessary for this
series. Maybe somebody with a bit more UI experience could chime in
here:

One is not warned when RDNSS is not set. When configuring static
addresses inside a VM it is required to set a DNS server, but when using
SLAAC the VM is just not able to resolve URLs. Also the ubuntu installer
did not allow setting DNS manually, so this can cause some confusion.

Currently in the subnet tab there is the option to set DHCP Ranges. This
option currently does not do anything as EVPN does not support DHCP.
Combined with the fact that you can set a Managed DHCP option it seems
like this would start a DHCP Server. As there already exists and
override for this Panel to add the RA subnet options I think the Range
tab could be deleted here. Still it is a bit weird that then only for
EVPN Zones DHCP Ranges are deactivated, even though other Zones also do
not support them.




      parent reply	other threads:[~2026-11-02 14:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 15:41 [PATCH docs/manager/network/proxmox{-perl-rs,-ve-rs} v5 0/9] add IPv6 RA / SLAAC support to EVPN zones Hannes Laimer
2026-10-29 15:41 ` [PATCH proxmox-perl-rs v5 1/9] pve-rs: sdn: add IPv6 RA builder binding Hannes Laimer
2026-10-29 15:41 ` [PATCH proxmox-ve-rs v5 2/9] frr: add IPv6 router advertisement support Hannes Laimer
2026-10-29 15:41 ` [PATCH proxmox-ve-rs v5 3/9] ve-config: sdn: add IPv6 router advertisement settings Hannes Laimer
2026-10-29 15:41 ` [PATCH pve-manager v5 4/9] ui: sdn: add IPv6 RA / SLAAC support Hannes Laimer
2026-11-02 13:53   ` Lukas Sichert
2026-10-29 15:41 ` [PATCH pve-network v5 5/9] sdn: evpn: derive IP version from CIDR for gateway-less subnets Hannes Laimer
2026-10-29 15:41 ` [PATCH pve-network v5 6/9] sdn: evpn: accept untracked IPv6 neighbor advertisements Hannes Laimer
2026-10-29 15:41 ` [PATCH pve-network v5 7/9] sdn: evpn: add IPv6 RA / SLAAC support Hannes Laimer
2026-10-29 15:41 ` [PATCH pve-network v5 8/9] api: vnets: include the zone type in the vnet list Hannes Laimer
2026-10-29 15:41 ` [PATCH pve-docs v5 9/9] sdn: add IPv6 RA / SLAAC section Hannes Laimer
2026-10-30 15:07 ` [PATCH docs/manager/network/proxmox{-perl-rs,-ve-rs} v5 0/9] add IPv6 RA / SLAAC support to EVPN zones Lukas Sichert
2026-10-30 16:30   ` Lukas Sichert
2026-11-02 14:25 ` Lukas Sichert [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=DMKSM1CTXTLF.ENLD69OZ1NO5@proxmox.com \
    --to=l.sichert@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal