From owner-freebsd-bugs@FreeBSD.ORG Sun Dec 31 00:00:42 2006 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4DA6C16A403 for ; Sun, 31 Dec 2006 00:00:42 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 173F413C461 for ; Sun, 31 Dec 2006 00:00:42 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kBV00fWY040300 for ; Sun, 31 Dec 2006 00:00:41 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kBV00fFj040299; Sun, 31 Dec 2006 00:00:41 GMT (envelope-from gnats) Resent-Date: Sun, 31 Dec 2006 00:00:41 GMT Resent-Message-Id: <200612310000.kBV00fFj040299@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, ScrewLoose Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 36D2F16A403 for ; Sat, 30 Dec 2006 23:57:27 +0000 (UTC) (envelope-from screwloose@infomaniax.homeip.net) Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by mx1.freebsd.org (Postfix) with ESMTP id EE44813C461 for ; Sat, 30 Dec 2006 23:57:26 +0000 (UTC) (envelope-from screwloose@infomaniax.homeip.net) Received: from [172.23.170.142] (helo=anti-virus02-09) by smtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1H044i-0005je-J4 for FreeBSD-gnats-submit@freebsd.org; Thu, 28 Dec 2006 22:50:12 +0000 Received: from [82.42.233.19] (helo=infomaniax.homeip.net) by asmtp-out1.blueyonder.co.uk with smtp (Exim 4.52) id 1H044i-00069n-3d for FreeBSD-gnats-submit@freebsd.org; Thu, 28 Dec 2006 22:50:12 +0000 Received: (qmail 1620 invoked by uid 1001); 28 Dec 2006 22:50:10 -0000 Message-Id: <20061228225010.1619.qmail@infomaniax.homeip.net> Date: 28 Dec 2006 22:50:10 -0000 From: ScrewLoose To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: ScrewLoose Subject: conf/107364: pf fails to start on bootup after system update from FreeBSD 6.1-RELEASE X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ScrewLoose List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Dec 2006 00:00:42 -0000 >Number: 107364 >Category: conf >Synopsis: pf fails to start on bootup after system update from FreeBSD 6.1-RELEASE >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Dec 31 00:00:41 GMT 2006 >Closed-Date: >Last-Modified: >Originator: screwloose >Release: FreeBSD 6.2-PRERELEASE i386 >Organization: none >Environment: System: FreeBSD silentsid 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #4: Thu Dec 28 03:17:47 GMT 2006 root@silentsid:/usr/obj/usr/src/sys/SILENTSID i386 The machine is running as a router for my home network, it also provides services such as file sharing. It runs FreeBSD 6.2-PRERELEASE on standard i386 hardware. >Description: After upgrading from 6.1-RELEASE from sources via cvsup to 6.2-PRERELEASE I discovered on the next reboot that PF had not been executed. I then checked the rc.conf man page to verify that my settings in /etc/rc.conf were still valid and they are. The settings I am using are pf_enable="YES" and all the other pf options are set to the defaults set out in /etc/defaults/rc.conf as described in the rc.conf man page. Following that I checked that I could run the /etc/rc.d/pf script by running it manually, a further check using "/sbin/pfctl -s" all presented me with all the rules I would have expected before the sy stem update. >How-To-Repeat: I have not tried to re-produce the environment for this error as it is a running live system and I do not want to cause more issues, by this I mean by downgrading/upgrading. To rediscover the error all that needs to be done is to reboot the system and to check for loaded pf rules. description. >Fix: Workarounds are 1. Run PF manually, 2. Add in a line to run it via rc.local (currently in use). >Release-Note: >Audit-Trail: >Unformatted: