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 372B31FF0B7 for ; Fri, 30 Oct 2026 17:30:41 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 3DE5B21611; Fri, 30 Oct 2026 17:30:37 +0100 (CET) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Fri, 30 Oct 2026 17:30:32 +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: "Lukas Sichert" , "Hannes Laimer" , References: <20261029154148.2882594-1-h.laimer@proxmox.com> In-Reply-To: X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1793377832924 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.568 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: XAG6VAC734ZRR3VKFYK3BTMRCLLRGNI6 X-Message-ID-Hash: XAG6VAC734ZRR3VKFYK3BTMRCLLRGNI6 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-30 16:07, Lukas Sichert wrote: > On 2026-10-29 16:41, Hannes Laimer wrote: > >> This series adds IPv6 Router Advertisement / SLAAC support to EVPN >> zones. > > I have only tested this very briefly on a three node cluster with an > existing IPv6 EVPN zone. After enabling 'Send Router Advertisements' on > a vnet called 'evpnet' and applying, then disabling and applying again, > the task exits with a warning. Going by the tasklog it seems to be > trying to remove the interface from frr even though it is still up: As discussed off list this is not actually harmful, just a bit noisy. FRR refuses to delete an interface that is still up, so any time a whole 'interface ' block disappears from frr.conf, frr-reload.py fails the same way. Removing an interface from a fabric triggers the same task warning. The failed reload falls back to restarting frr, which leaves the configuration in the correct state, and the next Apply is clean. So this is not something this series needs to fix. Sorry for the noise.