DNSBL Service won't start

Rockjansky

If I try and enable it through the web interface, I check the enable dnsbl box, and click save. It dumps me back to the same screen with the checkbox unchecked. If I look in services the dnsbl web service is present but it cannot be started there either. So… I'm trying to enable it but it won't stick.

Thanks

RonpfS

Maybe try with another browser
Or reinstall pfBlockerNG.
You are using DNS Resolver ?

jeffhoge

I can confirm 100% that I'm having these exact symptoms. It's a brand new SG-1000. I have even factory defaulted the SG-1000 and attempted to turn on DNSBL as the first setting (with no other changes in place after the initial setup wizard). I check the "Enable DNSBL" box, click save, and the browser window refreshes… then the "Enable DNSBL" box isn't ticked anymore.

I've tried this on Chrome, FF, IE, and even Safari for IOS.

Version: 2.4.0.b.20170601.1457

Rockjansky

Looks like maybe we found a bug. Is it possible to try and start the service through SSH? I'm wondering if there is a more verbose error message it displays when using the console.

BBcan177

Its odd that they are both the SG-1000 units… There has been no issues with any other hardware and no recent code change... Can you change settings in the pfBlockerNG General Tab? or any other pfSense tabs?

Do you see anything in the pfsense system log? or the Diag Backup config history?

I'll try to fire up the SG-1000 that I have and see if I can reproduce it...

BBcan177

Can you guys send me the output of the following command:

grep -A50 "<pfblockerngdnsblsettings>" /conf/config.xml</pfblockerngdnsblsettings>

Update:

https://redmine.pfsense.org/issues/7624

Did you guys install or uninstall any other packages recently?

Rockjansky

Output from the command below. I had Squid and Bandwidth D installed originally, but after the reset, just pfBlocker and AutoConfigBackup. I can reset again if you'd like, Also, I can enable and disable the pfBlockerng just fine.

<pfb_dnsvip>10.10.10.1</pfb_dnsvip>
<pfb_dnsport>8081</pfb_dnsport>
<pfb_dnsport_ssl>8443</pfb_dnsport_ssl>
<dnsbl_interface>lan</dnsbl_interface>

<dnsbl_allow_int></dnsbl_allow_int>
<action>Disabled</action>
<aliaslog>enabled</aliaslog>
<autoaddrnot_in></autoaddrnot_in>
<autoports_in></autoports_in>
<aliasports_in></aliasports_in>
<autoaddr_in></autoaddr_in>
<autonot_in></autonot_in>
<aliasaddr_in></aliasaddr_in>
<autoproto_in></autoproto_in>
<agateway_in>default</agateway_in>
<autoaddrnot_out></autoaddrnot_out>
<autoports_out></autoports_out>
<aliasports_out></aliasports_out>
<autoaddr_out></autoaddr_out>
<autonot_out></autonot_out>
<aliasaddr_out></aliasaddr_out>
<autoproto_out></autoproto_out>
<agateway_out>default</agateway_out>
<alexa_enable></alexa_enable>
<alexa_count>1000</alexa_count>
<alexa_inclusion>ca,co,com,io,net,org</alexa_inclusion>

<pfb_dnsvip>10.10.10.1</pfb_dnsvip>
<pfb_dnsport>8081</pfb_dnsport>
<pfb_dnsport_ssl>8443</pfb_dnsport_ssl>
<dnsbl_interface>lan</dnsbl_interface>

<dnsbl_allow_int></dnsbl_allow_int>
<action>Disabled</action>
<aliaslog>enabled</aliaslog>
<autoaddrnot_in></autoaddrnot_in>
<autoports_in></autoports_in>
<aliasports_in></aliasports_in></config></pfblockerngdnsblsettings>

BBcan177

@Rockjansky:

Output from the command below. I had Squid and Bandwidth D installed originally, but after the reset, just pfBlocker and AutoConfigBackup. I can reset again if you'd like, Also, I can enable and disable the pfBlockerng just fine.

<pfblockerngdnsblsettings><config><pfb_dnsbl>on</pfb_dnsbl>

<tldblacklist></tldblacklist></config>
<config><pfb_dnsbl>on</pfb_dnsbl></config></pfblockerngdnsblsettings>

As per the redmine that I posted above, this is the same issue… Something has added a dummy tags.
Also noticed that there is a second <config>below that…. So not sure what else can be messed up with the config.xml? JimP fix a bug in pfSense pkg_edit.php as you can see from the redmine. So make sure you download the lastest version to get this fix.

Two OPTIONS:

Edit the /conf/config.xml and remove every tag between:

and save the file. Just note that a typo in this file will cause a crash, so only do this if you know what your doing.

Then rm /tmp/config.cache which will reload the new config

Wipe the box any reinstall… And don't restore this config.xml as its corrupted...

Make sure you have a backup before proceeding with these changes!</config>

jeffhoge

Thank you! I performed the upgrade, deleted probably 100 lines in config.xml between the tags you indicated, deleted the config cache file, and rebooted (for good measure). Now DNSBL is allowing me to enable it, and leave it enabled this time.

Thanks again.

Rockjansky

Working for me as well. Thanks for your help!