Skip site navigation (1)Skip section navigation (2)
Date:      28 Dec 2006 22:50:10 -0000
From:      ScrewLoose <projectbugspam@gmail.com>
To:        FreeBSD-gnats-submit@FreeBSD.org
Cc:        ScrewLoose <projectbugspam@gmail.com>
Subject:   conf/107364: pf fails to start on bootup after system update from FreeBSD 6.1-RELEASE
Message-ID:  <20061228225010.1619.qmail@infomaniax.homeip.net>
Resent-Message-ID: <200612310000.kBV00fFj040299@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>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:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061228225010.1619.qmail>