pfBlockerNG-devel v3.1.0_7 / v3.1.0_14
-
@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. -
@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.
-
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!
-
-
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 -
@thexman it's the same file. I didn't see any reports about 2.6.
-
@bbcan177
Thanks! I can't wait to see if it will allow me to go back to Python Mode. -
-
@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
-
@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.
-
@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.
-
Awesome! I'm happy to do any testing that I can.
-
@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.
-
-
-