Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

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

    Scheduled Pinned Locked Moved pfBlockerNG
    50 Posts 14 Posters 12.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      SteveITS Galactic Empire @Alejo 0
      last edited by

      @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.

      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
      Upvote 👍 helpful posts!

      1 Reply Last reply Reply Quote 2
      • BBcan177B
        BBcan177 Moderator
        last edited by 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!

        "Experience is something you don't get until just after you need it."

        Website: http://pfBlockerNG.com
        Twitter: @BBcan177  #pfBlockerNG
        Reddit: https://www.reddit.com/r/pfBlockerNG/new/

        T 1 Reply Last reply Reply Quote 3
        • S SteveITS referenced this topic on
        • T
          TheXman @BBcan177
          last edited by

          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

          BBcan177B 1 Reply Last reply Reply Quote 0
          • BBcan177B
            BBcan177 Moderator @TheXman
            last edited by

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

            "Experience is something you don't get until just after you need it."

            Website: http://pfBlockerNG.com
            Twitter: @BBcan177  #pfBlockerNG
            Reddit: https://www.reddit.com/r/pfBlockerNG/new/

            T 2 Replies Last reply Reply Quote 0
            • T
              TheXman @BBcan177
              last edited by

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

              A 1 Reply Last reply Reply Quote 0
              • A AberDino referenced this topic on
              • A
                AberDino @TheXman
                last edited by

                @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 🙂

                1 Reply Last reply Reply Quote 0
                • T
                  TheXman @BBcan177
                  last edited by 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.

                  BBcan177B 1 Reply Last reply Reply Quote 0
                  • BBcan177B
                    BBcan177 Moderator @TheXman
                    last edited by 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.

                    "Experience is something you don't get until just after you need it."

                    Website: http://pfBlockerNG.com
                    Twitter: @BBcan177  #pfBlockerNG
                    Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                    T S 2 Replies Last reply Reply Quote 2
                    • T
                      TheXman @BBcan177
                      last edited by TheXman

                      @bbcan177

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

                      1 Reply Last reply Reply Quote 0
                      • S
                        seanmcb @BBcan177
                        last edited by

                        @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.

                        1 Reply Last reply Reply Quote 0
                        • fireodoF fireodo referenced this topic on
                        • BBcan177B BBcan177 unpinned this topic on
                        • GertjanG Gertjan referenced this topic on
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.