Ah, looks like the ASN source is returning errors right now. For example: https://api.bgpview.io/asn/6161/prefixes returns a 500 server error.

@gertjan

Okay, there's a bunch of Alphanumeric characters between "suppression" tags, and I used a hex64 -> ASCII to convert and bingo! You're right! Good to know...

Same for the other IPV4 lists.

Thanks a lot @Gertjan !

@akuma1x Thanks I will look these up. I like videos compared to text due to my learning style but the drawback is that there is the potential for wasted time due to older versions, superficial info or just plain lousy content which is why referrals is a good way to filter out the noise. Thanks again.

So I guess one solution would be to not reconnect the PPPoE connection from my side.
Another would be to let pfBlocker not create the rules but only aliases and to create the rules myself.

All in all I have a bad feeling regarding reconnecting the PPPoE connection in pfSense, often the web-UI is not accessible for some time, could be a more general problem.

While using pfsense 2.4.5.1 pfblockerng allowed the selection of AS Numbers. But that has disappeared in the 2.1.4_26 version supported by pfsense 2.5.2. Can anyone advise what happened or how I can block a site by ASN

@steveits God, totally misread the table, thanks! 👍

Yes, after upgrading to 3.1.0_4, everything is fine..
Thanks BBcan177 and pfsense team

@gertjan Upgraded to v3.1.0_4 (new one came out already?) and now it works! Thank you!

Updated to 3.1.0_4 a couples of minutes ago, and as usual I forgot to look at the state of unbound, and it was stopped of course.

But, what I do now is doing a full reload, as I see the yellow thingy :

2c281196-02a3-438a-a1df-2a08039ccfd5-image.png

and that will also take care of the unbound issue.

Hi,

After some troubleshooting, I found out the problem was with Private DNS (dns.google) setting on the phone. Once I set it to auto, everything turned out smooth again.

Thank you.

@pst said in Logging not working in 3.1.0_2:

@fireodo Thank you!

😊

@cool_corona said in pfBlockerNG-devel: Version 3.1.0_2 - Fix for #12706:

@gertjan Does it matter?

As https://redmine.pfsense.org/issues/12706 tells me :

Description How to reproduce: 1) Install pfBlockerNG-devel, and configure DNSBL in python mode 2) Enable RAM disk for /var 3) After reboot, all files associated with pfblockerng are deleted: /var/unbound/pfb_unbound.py /var/unbound/pfb_unbound_include.inc /var/unbound/pfb_py_hsts.txt 4) ...and unbound doesn't start:

But I have no RAM disks, as 'my case' is like many others : not much RAM, but loads of (SSD) disk space.
So, no step 2 for me. The issue becomes a none issue.
The issue is real, that's not the question.

Apparently being fixed in next release pfBlockerNG-devel v3.1.0_3:

https://github.com/pfsense/FreeBSD-ports/pull/1151

@fiblimitless

please ignore/delete my previous post.
When Global loggings Enabled, it takes priority, and is in effect, no matter the option shows inside the log's settings. when disabled, logs show back to what you changed it to.

@scorpoin

Goto the pfB logs page, select the error.log file and click on the waste bin.
Do an Update, reload, All.

If the error persists, wastebin the error.log file again.
Remove the incriminating feed.
Do an Update, reload, All.

@steveits There is no "Feeds" tab.
At the top I go to: Firewall -> PFBlockerNG
Then this is what I see in the image:

pfblocker.png

You were right. I was not using the "devel" version and was on the pfBlockerNG 2.1.4_26 version. I uninstalled this and installed the devel version. Now I see all the feeds. Thank you.

The patch and a filter restart did the job - thank you!