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 D863B1FF0BC for ; Thu, 29 Oct 2026 20:43:11 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 9F50E21425; Thu, 29 Oct 2026 20:43:09 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Subject: applied: [PATCH pve-firewall 1/1] rules: verify no interface is set for rules with direction forward Date: Thu, 29 Oct 2026 20:43:00 +0100 Message-ID: <179330297832.2066708.8341065255188237449.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260626122019.175700-1-s.hanreich@proxmox.com> References: <20260626122019.175700-1-s.hanreich@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1793302986384 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.426 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: X5GRFHPTDIY3C33WH35ZV45OM3RHEMDF X-Message-ID-Hash: X5GRFHPTDIY3C33WH35ZV45OM3RHEMDF X-MailFrom: t.lamprecht@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 Fri, 26 Jun 2026 14:20:17 +0200, Stefan Hanreich wrote: > It is not possible to specify the iface option for rules with > direction forward. This has not been verified by the backend, which > made it very easy to accidentally create invalid FORWARD chain rules. Applied, thanks! [1/1] rules: verify no interface is set for rules with direction forward commit: 09225d8fc90c3b24b248e29b832e7ff08c42eb88