Error loading the rules pfblockerNG
kiekar last edited by
I received several email notification today regarding loading rules.
There were error(s) loading the rules: /tmp/rules.debug:48: file "/var/db/aliastables/pfB_Whitelist.txt" contains bad data - The line in question reads : table <pfb_whitelist>persist file "/var/db/aliastables/pfB_Whitelist.txt"
After getting back home I rebooted pfSense and once again I received the same error message. I took a look at the rules.debug file but could not find anything out of the ordinary.
Any help would be much appreciated.
cmb last edited by
It's the /var/db/aliastables/pfB_Whitelist.txt that has bad data of some sort. Remove or fix that one.
I added improved validation on URL table aliases recently in 2.3, so bad data can't prevent the ruleset from loading.
What is in this Whitelist? Is it from a custom entry? or from a URL?
There should be sufficient validation in pfBlockerNG to avoid this issue, so post back and I will see if there are some corner cases.
kiekar last edited by
What is in this Whitelist? Is it from a the custom entry? or from a URL?
I used the IPv4 custom list with a list of 5 IP addresses. eg. 220.127.116.11/19
At the moment all seems fine after clearing the error messages and doing a second reboot.
Thats strange… That format should not trigger any errors?
If this happens again, PM me the whole custom list, a redacted /tmp/rules.debug and the contents of the file /var/db/aliastables/pfB_Whitelist.txt
attilahooper last edited by
I just got the same error
03-07-16 16:07:00 [ There were error(s) loading the rules: /tmp/rules.debug:36: file /var/db/aliastables/pfB_PRI2.txt contains bad data - The line in question reads : table persist file /var/db/aliastables/pfB_PRI2.txt] 03-07-16 18:02:39 [ There were error(s) loading the rules: /tmp/rules.debug:38: file /var/db/aliastables/pfB_PRI3.txt contains bad data - The line in question reads : table persist file /var/db/aliastables/pfB_PRI3.txt]
There are a few IPs in cidr.
Can you PM me the contents of those two files (If there still is an error)… I can't do much without seeing the file contents when there is an error message...