@cooLopke: So I guess there is no possible way to remove those ads in google search? DNSBL can't manipulate the Web page like a browser extension. So when you see (AD) in Google search, clicking on those may result in a blank page since DNSBL may be blocking those domains.

In theory you could install Privoxy on your pfSense box and setup a cron entry to download the adblock2privoxy lists, say every week? adblock2privoxy downloads page

@BBcan177: The file  /usr/local/www/pfblockerng/www/index.php https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG/files/usr/local/www/pfblockerng/www/index.php#L36 Just change the base_64 image to another image… Another similar thread:   https://forum.pfsense.org/index.php?topic=120253.0 That's exactly what I was looking for.  I'll be testing it out later today when I get home.

Also, it won't display the log information from the shell… So while the reload task does complete... its not reporting that data to the shell... It's important to review the log for any issues... You would need to run a tail command in another window: tail -f /var/log/pfblockerng/pfblockerng.log

I wish you could see me face palm myself. So the problem was I had my webconfigurator https port set on dnsbl's ssl port. Now the service shows a green check mark. Conflict…always seems to be my problem XD

Maybe you could try the other Rule order, where pfB_Pass/Match is before Block/Reject rules. Tried a different rule order. Worked perfectly. Thanks,

@BBcan177: The next version will have a new page that improves this layout… See the following: https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG/files/usr/local/pkg/pfblockerng/pfblockerng_sync.xml#L152-L153 The first entry is "http" and the second entry is "https" Thanks For that…  8)

You cannot unless you use 2.4. Limiters are broken with NAT.

Upgraded from 2.2, maybe I ended up with both. I'll try removing one.

If you are using Squid, you need to exclude the VIP from proxy.

It depends on your WAN FW rules. By default everything is blocked by the default Block rule. So adding single Permit rule from the "Selected GeoIPs" to the "Selected WAN Port(s)" to the "Selected Destination" should only allow those IPs to hit the open ports.

@BBcan177: See here: https://forum.pfsense.org/index.php?topic=124945.0 In my version of the file the line number is different and I also see several lines with identical content. I will wait for an official release. But thank you anyway.

See here: https://forum.pfsense.org/index.php?topic=124945.0

What about Firewall / pfBlockerNG / Alerts?

@Ibor: @BBcan177: The package has a feature to backup and restore the DNSBL database for RAMDisk installations. Where can I find that feature precisely? Thanks in advance! Its done automatically in the background when RAMDisks are enabled…. No real need to touch it...

@EDinATL: I had some particularly nasty ads popping up on my android which led me to want to manually block some ad servers via the DNSBL, so I eventually figured out how to do this today and used the method spoiler describes.  I found the process a bit confusing since the 'feeds' section would seem to be for feeds and not necessarily user defined lists.  At first I was manually editing a file in /var/unbound and mimicking the format used in pfb_dnsbl.conf which was cumbersome.  I was glad to find this method but I wish there had been kind of clue as to how to get there.  Thanks spoiler! Its not recommended to edit the /var/unbound/pfb_dnsbl.conf file as that will get overwritten on cron updates… The DNSBL Feeds Custom list is the easiest option to manually add Domains... You can also write the Domains to a text file accessible to the pfSense box (Local webserver) or on the pfSense box itself...  See the blue infoblock icons on the DNSBL Feed tab for more details...

@guardian: 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.xml But 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...

Are you using Safari?  I've only heard of issue with that browser :)  Not really much I can do about it…. Next release will have the option to sinkhole to 0.0.0.0 which will help with this issue.... But will also negate the logging feature.... So you could also just sinkhole to 0.0.0.0 for the domains that are causing these error messages.... But will have to wait for the next release... https://forum.pfsense.org/index.php?topic=102470.msg573329#msg573329

That is an optional rule. A permit firewall rule can be manually created to suit your network requirements… I will try to improve this to the next release ...