@RonpfS Moved to pfblockerng and it seems to be working fine.

@Ramosel said in Upgrade hangs: @Qinn Did reinstalling pfSense fix your issue? Yes, I installed 2.4.5-p1 and restored config and all is well.

@ChristianG solved :) Missconfiguration from my side was the problem.

used flex to remove the download errors but the service refuses to start. im still getting adblocking on the vpn so it seems to be working but not sure if the functionality is impaired or not

@Rico said in Cant find the old lists in the feed in pfblockerNG DEV.: Firewall > pfBlockerNG > DNSBL > DNSBL Groups > EasyList > EDIT You will see failed downloads in yellow. -Rico Thank you .)

Yeah that only works for firefox.. But I would put in all possible methods to block the nonsense that is doh.. I have that setup, I have firefox config setup to not use it, and I use a block list of known doh domains and block those.. Security and privacy my ASS.. It is just another way to monetize users.. It sure and the F is not about user privacy.. It is a slap in the face to all local controls - They are saying F you admins, we don't give 2 shits about your local controls - we want the user data, so we will let them send it to us directly! And good luck stopping us - we will just do it so it looks like normal web traffic..

Good morning, me too keeps going out of sync. As read above there may be duplicate entries but I can't find them in the log. Could you help me to see my log? Thanks, Alberto my log at this link link text

@cjbujold said in PfBlockerNG causing a network reset error.: Thank you for the feedback. Will definitely try the suggestions. But from your comments I think that Unbound will be the issue since the backups normally runs for about 15+ hours. If it is Unbound any suggestion on how to fix it? Thanks As @Gertjan said, pfBlocker and Unbound are functioning correctly and his detailed description is very good. Unless the pfBlockerNG list is explicitly blocking your backup, turning off the option to Kill States might solve the problem with your backup breaking. The downside would be if you have an infected system that is in communication with a malware site, (or any other undesirable activity that has the firewall open) and a new rule comes in to prevent the undesirable communication, that rule will not break the communication until the state times out or something else happens to reload the firewall states. Depending on how often the firewall is rebooted and/or configuration changes are made that could be days, weeks or even months. You may also wish to look at error.log in the pfBlockerNG log tab or from the shell: less /var/log/pfblockerng/error.log I found bad feeds files can also cause issues. You may need to temporarily disable or remove one or more feeds.

@MerinF01 Right, if you set the update settings to use the previous stable version, the package manager will show you the packages for 2.4.4.

@RonpfS said in PfblockerNG not showing all feeds in the widget: When you click on the under DNSBL Source Definitions you should see something like : Header/Label: This field must be unique. This names the file and is referenced in the widget.  (ie: Spamhaus_drop, Spamhaus_edrop) I guess it is the same for DNS Group Name, you have 4 FIREHOL , inspect the pfblockerNG log, it's probably getting mixed up with table. Change the DNS Group Name to be unique, Force Reload DNSBL, inspect the logs and see if things get better. [image: 1591778370775-53e9be1f-6964-4528-9244-c5fdbba6b0ad-billede.png] Worked like a charm. Thank you :) An update to the text could be a good idea so one can avoid this.

Hi, All these questions have been answered already by @BBcan177 - here, or on redmine. If I have some time, I'll Ctrl-F them for you and report back. @guardian said in pfBlockerNG vs pfBlockerNG-devel and how to migrate settings: Over the last year have there been any bad updates? From what I recall, no. And if so, a couple of hours and and update is pushed out.

@Gertjan That's fine, I thought you already have something. Thank you very much for your help :)

I know this thread is old but I have the same issue on two different machines. I'm using pfSense 2.4.5 stable and pfBlocker-NG devel 2.2.5_32. The IPv6 filtering works fine but I don't get any logs showing this. If I click on the "37" for the matched IPv6 addresses it shows nothing. [image: 1591508451848-unbenannt.jpg] [image: 1591508451877-unbenannt2.jpg]

Hello! I would recommend reading through all of the dropdown text under the little blue "infoicon" links for the TLD option and all of the whitelist/blacklist options on the pfb -> dnsbl page. There is some great info in there. John

the package maintainer's suggestion (BBcan177) for a long time is to use pfBlockerNG - devel (current - 2.2.5_32) there are plenty of fixes in it (also applies to GeoIP) [image: 1591203010595-5f4c0e7a-ac4a-4c90-9039-a439269d13c7-image.png] BTW: this also applies to the pfSense version (2.4.5)

I think I have this fixed now. I had a couple of lists reporting errors on downloading and that they were using previous data. As they had been down for a few weeks I decided to remove them and the error messages have stopped. These down lists had been giving giving errors for 2 weeks or more before this issue appeared.

My steps above worked with one addition...New Step #1...this most important...Backup the pfsense configuration before doing the rest. No issues, running -devel version now. I thought I had a problem because the exact day/time I did this was when the community wide package certificate issue was going on & I wasn't able to load packages. Works now. I would say my step #4 above is not necessary unless you have manually entered pfBlockerNG related custom options in the DNS Resolver. If not, the one that the system automatically places there during installation will also be removed when uninstalling.