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 0DA621FF186 for ; Sat, 4 Oct 2025 14:59:27 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 082B7122BD; Sat, 4 Oct 2025 14:59:28 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Date: Sat, 4 Oct 2025 14:58:42 +0200 Message-ID: <175958267535.2042357.17899189300726950965.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20250923122645.154759-1-s.hanreich@proxmox.com> References: <20250923122645.154759-1-s.hanreich@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1759582708804 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.027 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: [PATCH proxmox-firewall 1/1] fix #6831: move conntrack statement to forward chain 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" On Tue, 23 Sep 2025 14:26:43 +0200, Stefan Hanreich wrote: > The conntrack statement was included in the host-forward chain, which > is managed by the firewall daemon. It gets flushed in every iteration > of the daemon, but the rule is never re-created in the daemon. This > caused conntracked flows that are routed by the PVE host to not get > accepted. Generally, the ruleset is constructed in a way that all > chains that are managed by the firewall daemon are empty by default - > this was the only exception. Move the ct state statement to the > appropriate chain. Since the forward chain is in the inet table which > never sees ARP traffic in the first place, remove the respective > statement matching on ARP. This is most likely copied from the bridge > table where this modifier is indeed necessary, since there ARP traffic > is visible. > > [...] Applied, thanks! [1/1] fix #6831: move conntrack statement to forward chain commit: 70c65c07db51659070c3fe6f24bfe8f4b6479045 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel