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.

@dabone said in PFblockerng 2.2.1 with tdl, adding a schedule?: is there an easy way to schedule the block? There is no provision for scheduling in pfblockerNG.

Thanks!.

@matt1544 said in failed install pfBlockerNG-devel: 2.2.1 on pfSense-2.4.4.a.20180717.0730: Do you know what version of pfsense would be compatible? 2.4.3 or less

@bbcan177 Thank you for the reply. When I first got into Selective Routing last year on my Asus router, I also used the entware package whob to mine IPv4 addresses. I also discovered that it did not return the number of IPv4 addresses compared to ipinfo.io. Here is a snip of example code use to obtain IPv4 for a website. #Pull all IPs listed for whatismyipaddress.com on radb.net whob -h whois.radb.net -- '-i origin AS16625' | grep -Eo "([0-9.]+){4}/[0-9]+"' So, I went with ipinfo.io. I have since found two other similar sites. I too have been on the lookout for an alternative source. I will let you know if I find any.

I haven't got them working together yet. First I want to know if they can have conflicts with each other. I am using pfSense 2.4.3 and the latest versions of each product currently. These days I'll make them work together and I'll tell you anything new in this thread. Greetings Gabriel

Thank you very much for the quick reply. I hadn't considered the consequences of blocking India vs India_Rep. It turns out that entire subnet is controlled by Cisco and several of our Texas state counties are assigned IPs in that range. Since this "problem" only began after July 2nd (the last time they were able to connect to our mail server using that same IP), we assumed it was entered by mistake. I've informed our customer and they will get with Cisco to determine a resolution, as it seems they're also now being blocked by other mail servers as well as their hosted helpdesk app is failing. All of these problems began sometime after July 2nd, which is when I assume the IP was entered into the India_Rep database. Thanks again for your assistance! David

Nevermind - My bad, was a TLS configuration issue in Postfix!

@fredlubrano said in PHP Warning: Illegal string offset 'vip' in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 1128: amd64 11.2-RELEASE FreeBSD 11.2-RELEASE #35 79c8a561b61(RELENG_2_4_4): Mon Jul 9 16:25:18 EDT 2018 root@buildbot3:/builder/ce-master/tmp/obj/builder/ce-master/tmp/FreeBSD-src/sys/pfSense In pfSense 2.4.4, it moves to PHP v7 which changed how arrays are defined. Unfortunately, you will need to drop down a lower pfSense version until the package is reworked to address the new changes in PHP7.