/etc/pf.conf' is not readable?


#1

I got this error message at every boot time:

/etc/init.d/pf[1973]: pf: `/etc/pf.conf’ is not readable (because that is simply missing)
/etc/init.d/pf[1965]: ERROR: pf failed to start

Interesting because the TrueOS using the IPFW firewall I think :slight_smile: not the PF firewall.
Now I’m using the stable version of TrueOS, but I got this message in the earlier version (TrueOS-2017-07-05-x64-DVD.iso ) too.

===================
General information

boot environment now (N) … 12.0-CURRENT-up-20170908_205757 NR 2017-09-08
after restart ® … 12.0-CURRENT-up-20170908_205757 NR 2017-09-08
boot loader …………………………………… BSD
type ……………………… BIOS
CPU ………………………………………………………… Intel® Core™ i5-6200U CPU @ 2.30GHz
number of cores ……………… 4
host ……………………………………………………… host
memory ………………………………………………… 8192 MB available, 6565 MB free
OS git branch ……………………………………………………………………………………… trueos-stable
OS git revision ………………………………………………………………………………… ac2f0aa3b
OS kernel build time ………………………………………………………… Wed 2017 Jun 21 01:09:23 UTC
OS kernel identity …………………………………………… (uname -i) GENERIC
OS platform (architecture) ……………………… (uname -m) amd64
OS release level ………………………………………………… (uname -r) 12.0-CURRENT
OS version and patch level …… (freebsd-version) 12.0-CURRENT
TrueOS package set ………………… STABLE
TrueOS version …………………………… TrueOS-Desktop-201706210948
uptime ………………………………………………… 1:18
user …………………………………………………… root

More (TrueOS Desktop):

desktop environment …… Lumina
sound card driver ………… pcm0: <Realtek ALC255 (Internal Analog)> (play/rec) default
wireless driver ……………… iwm0
X11 drivers ………………………… intel_drv.so

#2

find /etc/runlevels -name “pf*” -print

Does that show pf has been added to any runlevel?
How about anything in /etc/rc.conf or /etc/defaults/rc.conf? (grep pf /etc/rc.conf, grep pf /etc/defaults/rc.conf)

(You need to work on your uptime:
uptime ………………………………………………… 91 days, 16:24

:wink:


#3

Hello mer!

Really thank’s your fast answer! I could solve this error with the help of your answer! The true is that I changed the behavior of some system services in the Service Manager and I changed the behavior of the pf - Packet Filter too.

My old and wrong setup:

Thank’s your help again! The error message gone! How secure is the “false” “false” setup?

My last and most important question is that the “uptime ………… 91 days” is your, is this true?


#4

Yep, uptime is true. Desktop system, only gets rebooted after power failure or system update (which will probably be on the 6 month stable schedule now).