How to recover and start over?
-
Is there a way to save my configuration so I can easily remove pfBlockerNG and just strart over without having to reenter the contents of the IPv4/ DNSBL Feeds? That's a ton of work!
I have been making so many changes as I try to figure things out, I suspect that I've found a bug where one of those changes didn't happen cleanly. I've got this error, and it doesn't seem to make sense.
Filter Reload
There were error(s) loading the rules: /tmp/rules.debug:26: cannot load "/var/db/aliastables/pfB_DNSBLIP.txt": No such file or directory - The line in question reads [26]: table <pfB_DNSBLIP> persist file "/var/db/aliastables/pfB_DNSBLIP.txt" @ 2017-01-26 16:44:20
There were error(s) loading the rules: /tmp/rules.debug:195: macro 'pfB_DNSBLIP' not defined - The line in question reads [195]: block return log quick on { em1 em1_vlan1 } inet from any to $pfB_DNSBLIP tracker 1770002969 label "USER_RULE: pfB_DNSBLIP AR" @ 2017-01-26 16:44:42I had a configuration that was sort of working and then I introduced VLANs. I've got to take a step back, and start over, and it would be easiest if I could just remove pfBlocker, and all it's rules/alias/configs/etc. fix my other problems and start over (but without having to reenter all the block lists).
Any input would be much appreciated. (Happy to work though the shell as well - especially if that would be easier.)
-
Take a look at the help text in the General Tab for "Enable" pfBlockerNG… Uncheck "Keep Settings" and save will wipe the previously downloaded files...
-
Take a look at the help text in the General Tab for "Enable" pfBlockerNG… Uncheck "Keep Settings" and save will wipe the previously downloaded files...
Thanks, I figured that part out…. the part that I really needed help with is:
Is there a way to save/resote the IPv4/ DNSBL settings? (Just the
It's a lot of work to try and reenter all that by hand in the GUI. -
Not easily…
The error message above is a minor error indicating that a rule was defined but there was no associated alias table. This can happen when the package settings are changed and a filter reload is still occuring in the background... So once you clear the message, as long as it doesn't repeat shortly after, its safe to ignore...
When you Disable the package, and have "Keep Settings" unchecked, that will remove the Firewall rules, Aliases etc... So there should really be no need to wipe and redo the work... Once its disabled... Check the Firewall Interface Tabs, Alises etc... Or just reboot after that... Then re-enable the package starting with one part at at time till you have it working as expected... so start with the IP component, and then add DNSBL following that... Just a suggestion...
Otherwise, post a concern, and we will try to help...
-
Thanks…. that's a great help. I should be able to work though this now.
I was wondering what would happen if I:
-
saved a copy of /usr/local/pkg/pfblockerng.xml
-
switched off pfBlockerNG
-
edited my copy, of pfblockerng.xml file
-
reloaded the edited copy of pfblockerng.xml to pfSense
-
then turned on pfBlockerNG
Assuming that the edits were minor and I didn't make a mistake would that work?
-
-
Thanks…. that's a great help. I should be able to work though this now.
I was wondering what would happen if I:
-
saved a copy of /usr/local/pkg/pfblockerng.xml
-
switched off pfBlockerNG
-
edited my copy, of pfblockerng.xml file
-
reloaded the edited copy of pfblockerng.xml to pfSense
-
then turned on pfBlockerNG
Assuming that the edits were minor and I didn't make a mistake would that work?
The pfblockerng.xml does not hold the configuration…. All configurations are saved in the pfSense config file:
/conf/config.xmlBut editing that file should only be done with extreme care, or you risk crashing the config….
You could also setup another box and use the "Sync" feature, that will push all the configuration to another box... and vice-versa...
-
