From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 45D641FF09C for ; Mon, 02 Nov 2026 15:26:00 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 8E33A21756; Mon, 02 Nov 2026 15:25:57 +0100 (CET) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 02 Nov 2026 15:25:52 +0100 Message-Id: Subject: Re: [PATCH docs/manager/network/proxmox{-perl-rs,-ve-rs} v5 0/9] add IPv6 RA / SLAAC support to EVPN zones From: "Lukas Sichert" To: "Hannes Laimer" , References: <20261029154148.2882594-1-h.laimer@proxmox.com> In-Reply-To: <20261029154148.2882594-1-h.laimer@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1793629552915 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.555 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: I4Z3PBY7MGP7QKBGRYMMUT5IUOQGQXW6 X-Message-ID-Hash: I4Z3PBY7MGP7QKBGRYMMUT5IUOQGQXW6 X-MailFrom: l.sichert@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On 2026-10-29 16:41, Hannes Laimer 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.