From owner-freebsd-bugs@FreeBSD.ORG Tue Oct 4 18:40:17 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58C6516A41F for ; Tue, 4 Oct 2005 18:40:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0FB443D49 for ; Tue, 4 Oct 2005 18:40:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j94IeGZO015984 for ; Tue, 4 Oct 2005 18:40:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j94IeGOQ015983; Tue, 4 Oct 2005 18:40:16 GMT (envelope-from gnats) Date: Tue, 4 Oct 2005 18:40:16 GMT Message-Id: <200510041840.j94IeGOQ015983@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: =?ISO-8859-1?Q?Vladim=EDr_Kotal?= Cc: Subject: Re: kern/86752: pf does not use default timeouts when reloading config file X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-1?Q?Vladim=EDr_Kotal?= List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 18:40:17 -0000 The following reply was made to PR kern/86752; it has been noted by GNATS. From: =?ISO-8859-1?Q?Vladim=EDr_Kotal?= To: bug-followup@FreeBSD.org, =?ISO-8859-1?Q?Vladim=EDr_Kotal?= Cc: Subject: Re: kern/86752: pf does not use default timeouts when reloading config file Date: Tue, 4 Oct 2005 20:38:10 +0200 This problem can be fixed by applying following patch: http://techie.devnull.cz/public/patches/pfctl-timeout.patch which makes behavior of options consistent with behavior of rules (within pf.conf). This means that global timeout settings will be applied only when ruleset is parsed successfully (which is not happening in current pf implementation) and also when lines with global timeout settings (or optimization lines) are removed, default timeout settings are restored. (also not happening in current pf implem.)