https://forum.netgate.com/topic/132669/pfblockerng-generating-php-errors/5

@ronpfs said in DisconnectAds, DisconnectTracking and DNSBL_Malicious - D_Me_Malw:

host -t A s3.amazonaws.com

Thanks Ronpfs it did the trick

host -t A s3.amazonaws.com s3.amazonaws.com is an alias for s3-1.amazonaws.com. s3-1.amazonaws.com has address 54.231.33.202

Did not new the command dig (domain information groper) thanks 👍

I've upgraded 2.1.2_3 to 2.1.4_8 without issue.

https://forum.netgate.com/post/780328

Fixit:

# pkg-static search icu icu-60.2_1,1 International Components for Unicode (from IBM) # pkg-static install -yf icu-60.2_1,1 # ln -s /usr/local/lib/libicui18n.so.60 /usr/local/lib/php/20131226/libicui18n.so.60

Restart php-fpm

Everything that is blocked is visible in the "Alerts Tab".

@ronpfs OK back up now, thanks..

@grimson said in pfblocker_devel:

You do know/understand that installed packages no longer show as an available package, as they are installed already?

lol yes, I was just wondering if the new version had the same stuff as the devel version.
It sort popped up out of the blue in the package list while I already had pfblocker installed so / I went and installed the pfblocker_devel version.
Maybe I was the only one who saw it.
The pfblocker_devel version I'm using now is excellent with all new feeds.
Now when I look at the package list I see the new version of pfblocker.

I'm thinking its time to fully uninstall the pfblocker_devel and go back to the pfblocker on the package list now lol
Looks like I'm the only one with the pfblocker_devel lol

Good to see Mr BBcan177 is back welcome home mate :)

cheers guys

With a little more troubleshooting I found the issue. I neglected adding in a firewall rule to allow the client access to the DNSBL VIP over ports 443 and 80.

Thanks for pointing that one out to me. I missed it, because I read this one, https://www.reddit.com/r/PFSENSE/comments/8lnugz/pfblockerng_devel_version_released/ ,which suggests it was only downloadable from the unstable branch, as I did not expect a development release in the stable branch... 😎

@bmcdonald1778

Anything that is blocked will be visible in the Alerts Tab and can be whitelisted/suppressed.

@ronpfs worked, thanks

@bbcan177 said in Update lists fail:

@qinn said in Update lists fail:

btw From what I've read, when I want to move over to the latest dev of pfblockerNG I have to first deinstall pfblockerNG and then install the dev version and all settings will be restored, is this the right way to move over to the dev version?

Yes I would just go to devel and see if that fixes your issue.... There are a ton of new features in devel....
https://www.reddit.com/r/PFSENSE/comments/8lnugz/pfblockerng_devel_version_released/

Also install the "Cron" package for pfSense and you can see the pfSense Cron tasks from there.

Thanks for your advise 👍 👍 hoping for a release soon, I don't care about an ETA, take your time and keep up the good work.

Did as instructed.

Will report back results.

@Steve_B Sorry to keep bothering you but I'm learning as I go. For the PFSense box that I built, I used a Gigabyte B360N with a built in Intel CNVi 2x2 802.11 wifi. How ever I can not see it while in PFSense .... is there a driver I need to install? if so could you be so kind as to point me in that direction.

You normally would not put any sort of rule on "outbound" wan..

Rules are evaluated as traffic enters an interface towards pfsense from the network that interface is connected too.

If you want to block something on your lan or opt or any other "lan" side network then you would place the block on the that interface.