pfBlockerNG-devel v3.1.0_7 / v3.1.0_14

fireodo

@jdeloach said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

That's the issue, there is no upgrade available. 3.1.0_8 is not available.

In my understanding the 3.1.0_7 is the actual version for pfsense 2.6.0 and the 3.1.0_8 is the actual version for pfsense+ 22.05.
Both versions 3.1.0_7 (for 2.6.0) and 3.1.0_8 (for 22.05) are heavyly owerwoked.
The version 3.1.0_6 on 2.6.0 had the same codebasis as 3.1.0_7 on 22.05.
The 3.1.0_14 is for the developer versions based on freeBSD 14 and PHP 8.1

Please correct me if I'm wrong.

BBcan177

@fireodo

Yes that is correct. One of the pfsense devs committed a release for pfSense plus and caused the version mismatch.

The devs also told me yesterday that there was a build error so _8 didn't build. But they informed me that it should have been available since yesterday. If you still don't see it. Post your hardware specs ie amd/Intel and pfSense version.

Squuiid

Ugh. Updated from a stable 3.1.0_7 to 3.1.0_8 last night and now DNS stops working after a few hours of uptime. This is running at a school and unbeknownst to me kids are sitting exams today!
Easy way to roll back or troubleshoot? Restarting Unbound does nothing. Any help would be hugely appreciated. Running 22.05 on a Negate 6100 Max (amd64).

Alejo 0

@squuiid

You should always create a backup before updating any package in case this happens ~~hence restoring your latest backup config is an easy way to fix the issue.~~ Edit: I was wrong, see @SteveITS replies below

If you don't know how to restore your settings from backup:

Diagnostics > Backup & Restore > Restore backup section > Restore Configuration

~~If you don't have a backup~~ I am out of ideas, sorry.

Alejo 0

@squuiid
I am having the same issues with the DNS not working after the update but restarting unbound does fix my issue althought restarting the service every time is definitely not ideal either.

SteveITS

@alejo-0 The config backup doesn't back up package code, in fact when it restores it will restore the latest package. I'm pretty sure it will reinstall them even if already installed and you're just restoring, but am not positive offhand.

@Squuiid Are you getting an "address already in use" error logged?

Alejo 0

@steveits

@steveits said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

The config backup doesn't back up package code

I think it does, unless you check the Skip packages option which is the default. At least, that is my understanding. Please feel free to correct me if I am wrong.

SteveITS

@alejo-0 That will back up the package configuration but not the binary files or PHP code. Just take a look at the the .xml file.

BBcan177

Been seeing some reports of DNS issues with pfSense 22.05 and v3.1.0_8. I can't reproduce this on my test box, but will have it run more tests to see if I can reproduce.

For those that are having this specific issue in 22.x ONLY:
Here is the previous pfb_unbound.py version which you could try and see if this resolves the issue.

Run this command to download the file and then restart Unbound for it to take effect:

curl -o /var/unbound/pfb_unbound.py "https://gist.githubusercontent.com/BBcan177/83a6f4002ede77e00de7f8c67edb7421/raw"

Thanks!

TheXman

Hi @bbcan177
For those of us experiencing DNS issues with Python Mode after upgrading to pfB-NG 3.1.0_7 on pfSense 2.6.0, could you also provide that version's pfb_unbound.py file?

Re:
https://forum.netgate.com/topic/176362/pfblockerng-devel-v3-1-0_7-update-unbound-issue/13

BBcan177

@thexman it's the same file. I didn't see any reports about 2.6.

TheXman

@bbcan177
Thanks! I can't wait to see if it will allow me to go back to Python Mode.

AberDino

@thexman said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

Thanks! I can't wait to see if it will allow me to go back to Python Mode.

Fixed it for me

TheXman

@bbcan177
After making a backup of the 3.1.0_7 file, I switched back to Python Mode, downloaded the old python file using the link that you provided, and did a force reload.

The very first thing that I noticed was that I no longer got an error saying that pfSense was unable to check its version. Then, I did several of the things that would usually cause unbound to stop responding. So far, I'm happy to say, Python Mode is working quite well with the 3.1.0_6 python file. As a matter of fact, I could swear that 3.1.0_7 with the 3.1.0_6 python file is using less CPU. I also don't see my state table filling up with FIN_WAIT states from RDNC (port 953). Lastly, I don't see the error in the unbound log that I would see right before becoming unresponsive, it would say something like "invalidateQueryInCache: qinfo not found in cache".

In any case, I'll keep monitoring. Thanks for providing the old python file.

BBcan177

@thexman thanks for reporting back!

I was waiting for someone to post what error they were seeing and I didn't get any helpful details. So I think that bit of info that you now provided helps diagnose the issue. I will post a fix for testing once I have it ready.

TheXman

@bbcan177

Awesome! I'm happy to do any testing that I can.

seanmcb

@bbcan177 said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

I was waiting for someone to post what error they were seeing and I didn't get any helpful details. So I think that bit of info that you now provided helps diagnose the issue. I will post a fix for testing once I have it ready.

I'm a bit confused as to the current status of things... The current version I see available is 3.1.0_9. Does it have a known bug related to DNS getting sometimes broken? Thanks.