@bainsley said in new user and not sure about these log entries?:
What is the firewall syncing with? the kernel? BSD? Which filter? The rules?
The kernel includes capabilities what I would call a "IP stack". And it can act as a firewall.
Both are needed so the FreeeBSD kernel can do it's firewall thing, and that's what pfSense is all about.
Firewall rules are dynamically reloaded after many possible sirconstances, like processses restarting, alaiase changed, or some user GUI intercation. many others exist.
So you will see this :
@bainsley said in new user and not sure about these log entries?:
check_reload_status 400 Reloading filter
check_reload_status 400 Syncing firewall
a lot.
If you are not using IPSEC, this :
@bainsley said in new user and not sure about these log entries?:
php 414 rc.bootup The command '/usr/local/sbin/strongswanrc stop' returned exit code '1', the output was strongswan not running? (check /var/run/daemon-charon.pid)
is just a message that pfSense stopped IPSEC - and it was already stopped.
@bainsley said in new user and not sure about these log entries?:
php 414 rc.bootup. Creating rrd update script
This happens when pfSense finds a 'new' interface or object to make graphs for.
The graph data is stored in a so called rrd file.
A scripts that runs every xx seconds, populates the rrd file with data .
So you can have, after a while :
9cc0b9bc-bbd5-43ca-a771-a05bffd2cf8f-image.png
