From owner-freebsd-pf@freebsd.org Fri Mar 23 11:00:27 2018 Return-Path: Delivered-To: freebsd-pf@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23BDFF5FAE2 for ; Fri, 23 Mar 2018 11:00:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B16086D671 for ; Fri, 23 Mar 2018 11:00:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id DE18A16180 for ; Fri, 23 Mar 2018 11:00:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2NB0Pn0030670 for ; Fri, 23 Mar 2018 11:00:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2NB0PMN030662 for freebsd-pf@FreeBSD.org; Fri, 23 Mar 2018 11:00:25 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-pf@FreeBSD.org Subject: [Bug 226850] [pf] Matching but failed rules block without return Date: Fri, 23 Mar 2018 11:00:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: vegeta@tuxpowered.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-pf@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 11:00:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226850 --- Comment #2 from vegeta@tuxpowered.net --- I'm sorry but I did not bother to check OpenBSD syntax. Isn't FreeBSD diver= ted beyond the point of caring about it anyway? There are other ways to handle this without changing rule syntax, but then = it would not be tunable per rule: 1. have all "pass" rules always return if they fail 2. add new pf.conf "set" option 3. follow global "set block-policy" option Option 3 is the least invasive one but is not a solution for my particular issue - I want the firewall to silently drop packets when there is no match= ing rule but be verbose when a rule fails. I will prepare a patch for solution 2. That would mean no change in rule syntax, no change in default behaviour and possibility to enable this fix if anybody finds this to be a bug for them too. To be honest doing it this way also means I can easily implement it in my environment. The patch I prepared yesterday would require me to change how rules are generated depending on FreeBSD release and kernel patch level. Single change in pf.conf is way eas= ier to do as I create the resulting pf.conf from multiple files coming from different sources. --=20 You are receiving this mail because: You are the assignee for the bug.=