0_1548273582577_Screenshot_2019-01-23 pf100se ici - Firewall pfBlockerNG.png

Did you disable pfblockerNG before removing the package?

You could try to uncheck both, save, then remove the package.

Reinstalling the package seems to have done the trick.

Thanks for the reply, Johnpoz. Turns out that some of the firewalls/antiviruses in the Mac are messing with the DNS. Everything is working fine on systems that don't have that junk.

Attaching the /conf pkg-log text file which appears that the install is in good order.
0_1547868374225_pkg_log_pfSense-pkg-pfBlockerNG-devel-2.txt.zip

Install Cron package and then you could run a cron shell job 15 min before PfblockerNG Cron Update that download and process the list to a local file to be ready for processing.

So I should edit my port forward rules in NAT to add the a network alias for pfBlocker_NA IPv4 and IPv6.
Like this

Alias
0_1547228457662_fpBlocker Network Alias.jpg

Port Forward rule
0_1547228503649_ForwardRule.jpg

@bbcan177 said in Why is so difficult to block this specific website when using mobilephone's Chrome App?:

d its not possible to block that easily since its not on port 53.

so gettin you right
for optimal filter (pfB / DNSBL) experience it will be wise to
not redirect to port 53 (as i mentioned in the work around)

thanks for input ... makes totally sense
br from snowLand

and unbound reloads instantaneously

CoinBlocker feed is on gitlab.io, so maybe that is being blocked? Can you get to that domain?

The Dyre feed is down. Not sure when it will return. The other Abuse feeds came back online tho:
https://www.reddit.com/r/pfBlockerNG/comments/a6zs1u/abuse_sslbl_is_back_online/

@bbcan177 Thank you. I did that and it works!

WORKED LIKE A CHARM !

thx !

@veldthui said in Getting a list of .bid IP's:

and have not had any spam for the last two days.

Music to my ears :)

@tippet5x said in PfBlockerNG Error:

pfSense-pkg-pfBlockerNG: 2.1.4_14 [pfSense]

Update to pfBlockerNG v2.1.4_16 which has this issue fixed... You can also move to pfBlockerNG-devel which is much improved.

Sorry, after further testing, unbound is needing to be manually stopped if pfblocker is enabled in order to make setting changes to DNS resolver. Not the pfblocker services.

Do DNS resolver config changes work fine for you both without needing to manually interfere with stopping unbound? I just find it odd cause ive done 3-4 reinstalls lately and it’s presented this problem to me in all instances.

The only thing that I guess has changed as of recently is using the devel release. I don’t recall having to manually stop unbound previously.

Anyway, this can be marked as resolved as I don’t know if this is how it’s intended to be but I’ve managed a workaround.

Cheers for the awesome package BBcan! It’s some great stuff. I’ll flick you a donation to show my appreciation.

Hi, I believe I had run into this exact issue myself and this happened upon across multiple installs of it too.

I narrowed it down to the fact that some of the log files were not being created for any odd reason. For each of the log files, make sure they exist, and if they don't, manually create them using touch.

More info here.... I'd like to add a page for this in the GUI, but too much to do with so little time....
https://www.reddit.com/r/pfBlockerNG/comments/9vwkmm/ip_ranges_for_amazon_aws/

ps - Come and subscribe to the reddit page :)