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 25C3E1FF186 for ; Fri, 1 Aug 2025 17:43:57 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1B6481D9DE; Fri, 1 Aug 2025 17:45:25 +0200 (CEST) From: "Max R. Carrara" To: pve-devel@lists.proxmox.com Date: Fri, 1 Aug 2025 17:45:20 +0200 Message-Id: <20250801154521.594077-1-m.carrara@proxmox.com> X-Mailer: git-send-email 2.39.5 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1754063107989 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 0/1] Silence ebtables Audit Messages in dmesg 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 Cc: Wolfgang Bumiller Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Silence ebtables Audit Messages in dmesg - RFC v1 ================================================= In short, this is done by switching the `update-alternatives` calls in pve-firewall.service from ebtables-legacy / iptables-legacy to ebtables-nft / iptables-nft. Switching to ebtables-nft in particular silences the audit log spam one encounters after upgrading a PVE 8.4 node to PVE 9. This should be alright as the original bug appears to be fixed [1]. As the bug for iptables [0] appears to be fixed as well, switch to iptables-nft (and ip6tables-nft), too. ! ! ! NOTE ! ! ! ---------------- Switching to {eb,ip}tables-nft might come with some very subtle consequences that aren't really explained anywhere. Moreover, the nft subsystem probably handles things completely differently, as Wolfgang pointed out off-list. Both versions seem to have slightly different featuresets that can be determined by diffing their respective manpages--for example, so see how the -nft versions differ from the -legacy ones, it's possible to do the following (in bash / zsh, as the penguin operator isn't in sh): diff -u <(man ebtables-legacy) <(man ebtables-nft) | less diff -u <(man iptables-legacy) <(man iptables-nft) | less Since the original change is referred to "a bit of a hack" [2], consider this "a bit of a hack" as well, so be wary when applying this. I'll have this run in my test cluster and my workstation for a bit until I'm really sure that this doesn't cause any unintended side-effects. Wanted to send this out for now while I'm reading up on everything, so that others could have a look at least and install it on their own setups for testing purposes. References ---------- [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929527 [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929976 [2]: https://git.proxmox.com/?p=pve-firewall.git;a=commit;h=c743e671dad7a36871b6ab8e061e4200e64a4f54 Summary of Changes ------------------ Max R. Carrara (1): pve-firewall.service: update-alternatives to {ip,eb}tables-nft debian/pve-firewall.service | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel