From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 393F41FF186 for ; Fri, 1 Aug 2025 17:44:29 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3FF811DB03; Fri, 1 Aug 2025 17:45:57 +0200 (CEST) From: "Max R. Carrara" To: pve-devel@lists.proxmox.com Date: Fri, 1 Aug 2025 17:45:21 +0200 Message-Id: <20250801154521.594077-2-m.carrara@proxmox.com> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20250801154521.594077-1-m.carrara@proxmox.com> References: <20250801154521.594077-1-m.carrara@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1754063110031 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.085 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 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] [RFC pve-firewall v1 1/1] pve-firewall.service: update-alternatives to {ip, eb}tables-nft 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" Back in c743e671d it was necessary to update-alternative `ebtables` to `ebtables-legacy` due to some bugs [0][1]. However, these bugs appear to be fixed now. In Trixie, `ebtables-legacy` seems to cause an enormous amount of audit message spam in `dmesg` after upgrading from Bookworm--about 5 long lines every ~10 seconds-- making it very tedious to find anything one actually cares about. Thus, use the -nft variants instead of the -legacy ones as the aforementioned bugs have since long been fixed and the audit log spam is silenced that way. [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929527 [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929976 Signed-off-by: Max R. Carrara --- debian/pve-firewall.service | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/debian/pve-firewall.service b/debian/pve-firewall.service index f95ce6d..c99db26 100644 --- a/debian/pve-firewall.service +++ b/debian/pve-firewall.service @@ -8,9 +8,9 @@ Before=shutdown.target Conflicts=shutdown.target [Service] -ExecStartPre=-/usr/bin/update-alternatives --set ebtables /usr/sbin/ebtables-legacy -ExecStartPre=-/usr/bin/update-alternatives --set iptables /usr/sbin/iptables-legacy -ExecStartPre=-/usr/bin/update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy +ExecStartPre=-/usr/bin/update-alternatives --set ebtables /usr/sbin/ebtables-nft +ExecStartPre=-/usr/bin/update-alternatives --set iptables /usr/sbin/iptables-nft +ExecStartPre=-/usr/bin/update-alternatives --set ip6tables /usr/sbin/ip6tables-nft ExecStart=/usr/sbin/pve-firewall start ExecStop=/usr/sbin/pve-firewall stop ExecReload=/usr/sbin/pve-firewall restart -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel