Fresh Pfsense install giving tons of errors
-
I just got my pfsense box up and running again a few weeks ago, and all of sudden without me making any changes I've started to get tons of errors. I don't know what I need to do to fix this since it no longer can access the internet..
I got these errors
There were error(s) loading the rules: pfctl: /tmp/rules.debug: No such file or directory - Array @ 2024-08-01 20:21:49
There were error(s) loading the rules: invalid netmask '/2:' - The line in question reads [0]: @ 2024-08-01 20:22:41
There were error(s) loading the rules: invalid netmask '/2:' - The line in question reads [0]: @ 2024-08-01 20:22:45Crash report is attached..
-
@madbeefer said in Fresh Pfsense install giving tons of errors:
I don't know what I need to do to fix this since it no longer can access the internet..
That's why the console access exists : the repair is done on the device, not somewhere on the internet.
The error :
pfctl: /tmp/rules.debug: No such file or directory
The firewall control program couldn't find the file that contains all the firewall rules.
Knowing that the firewall (called 'pf') contains for all interfaces a 'DROP' rule by default : no traffic can enter no where anymore. This is a safe situation, but you've noticed the consequence : no more access.
That's why the console access exists.The question is : why this error ?
Does the file exist ?
Can you 'cat' (=show it) it ?
Console menu option 8, and then :cat /tmp/rules.debug
Look also here : How to Run a pfSense Software File System Check (5/2020) and do what is proposed, as that might be the issue : file system dirty, so it's read only, so "/tmp/rules.debug" couldn't be created. This situation can be created by switching the power down without doing a clean, admin initiated, shut down.
Furthermore : it looks like the file does exist, but contains 'wrong' info :
There were error(s) loading the rules: invalid netmask '/2:' ....
There were error(s) loading the rules: invalid netmask '/2:' ....Can you show us these rules ?
-
Hmm, two panics shown there in different processes and different backtraces.
I would run some memory tests to be sure it's not just bad RAM.
Steve