From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 7BC0D1FF185 for ; Mon, 4 Aug 2025 18:43:51 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B380E3704C; Mon, 4 Aug 2025 18:45:20 +0200 (CEST) Message-ID: <4538806b-38c0-4900-9c0c-231e9bc378b9@proxmox.com> Date: Mon, 4 Aug 2025 18:45:16 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta To: Proxmox VE development discussion , Stefan Hanreich References: <20250804140152.423614-1-s.hanreich@proxmox.com> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <20250804140152.423614-1-s.hanreich@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1754325897875 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.030 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] applied-series: [PATCH manager/network v2 0/2] do not apply FRR configuration when reloading host network configuration X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Am 04.08.25 um 16:01 schrieb Stefan Hanreich: > The FRR apply function was called when omitting the skip_frr parameter, which is > the case when saving the host network configuration via the Web UI, leading to > an enabled FRR daemon after saving the network configuration. > > In a follow-up we should also consider checking if the previous configuration > contained FRR entities, but the new one doesn't and disable the FRR daemon in > this case. > > Changes from v1 to v2: > * rebase on top of current master > > pve-manager: > > Stefan Hanreich (1): > api: network: default to not regenerating the frr configuration > > PVE/API2/Network.pm | 7 ++++--- > bin/pve-sdn-commit | 4 ++-- > 2 files changed, 6 insertions(+), 5 deletions(-) > > > pve-network: > > Stefan Hanreich (1): > sdn: api: rename parameter from skip-frr to regenerate-frr > > src/PVE/API2/Network/SDN.pm | 10 ++++------ > 1 file changed, 4 insertions(+), 6 deletions(-) > > > Summary over all repositories: > 3 files changed, 10 insertions(+), 11 deletions(-) > applied, thanks! _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel