conf/107364: pf fails to start on bootup after system update from FreeBSD 6.1-RELEASE

ScrewLoose projectbugspam at
Sat Dec 30 16:00:42 PST 2006

>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
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Dec 31 00:00:41 GMT 2006
>Originator:     screwloose
>Release:        FreeBSD 6.2-PRERELEASE i386
System: FreeBSD silentsid 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #4: Thu Dec 28 03:17:47 GMT 2006 root at 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.

        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.

        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.


        Workarounds are 1. Run PF manually, 2. Add in a line to run it via rc.local (currently
in use).


More information about the freebsd-bugs mailing list