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

    pfBlockerNG-devel v3.2.0_15

    Scheduled Pinned Locked Moved pfBlockerNG
    47 Posts 21 Posters 8.4k 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.
    • QinnQ
      Qinn @Unoptanio
      last edited by

      @Unoptanio if you cannot get in GUI and load this line in your browser it might work, of course with your login password

      Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
      Firmware: Latest-stable-pfSense CE (amd64)
      Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

      UnoptanioU 1 Reply Last reply Reply Quote 0
      • UnoptanioU
        Unoptanio @Qinn
        last edited by Unoptanio

        @Qinn
        I have now restored a backup from files I made in August.
        The only problem is that after the restore it takes me back to version 23.09.1 ​​with all the packages in old versions. At this point if I update to version 24.06_1 when doing the final reboot the gui stall problem I initially had occurs again.

        pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
        CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
        n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

        1 Reply Last reply Reply Quote 0
        • LarryFahnoeL
          LarryFahnoe
          last edited by

          I solved my problem by following @stephenw10 suggestions on this thread: https://forum.netgate.com/post/1185688 Thanks Stephen!!

          Also needed to kill off a pfblockerng.php cron process left over from the prior devel version.

          --Larry

          1 Reply Last reply Reply Quote 1
          • P
            peroni5
            last edited by

            ... 3.2.0.16 is out

            2x DDWRT 3.0
            APU2C4 mit pfsense 2.4

            UnoptanioU GertjanG 2 Replies Last reply Reply Quote 0
            • UnoptanioU
              Unoptanio @peroni5
              last edited by

              @peroni5
              Have you tried, does it work?

              pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
              CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
              n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

              1 Reply Last reply Reply Quote 0
              • GertjanG
                Gertjan @peroni5
                last edited by

                @peroni5 said in pfBlockerNG-devel v3.2.0_15:

                ... 3.2.0.16 is out

                Yeah, saw that.
                Did a save, a ZFS clone, rebootted from that, and installed the "16".
                Saw procs hitting 100 % again as this morning, so I bailed out. I'll give it a 7 days cool-down from now ^^

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                3 UnoptanioU 2 Replies Last reply Reply Quote 1
                • 3
                  3aandl @Gertjan
                  last edited by

                  @Gertjan 3.2.0_17 was released and install etc. is working as it should now

                  GertjanG 1 Reply Last reply Reply Quote 0
                  • UnoptanioU
                    Unoptanio @Gertjan
                    last edited by

                    @Gertjan

                    This is a great system for testing, ZFS Boot Environment.
                    Too bad it didn't occur to me

                    pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
                    CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
                    n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

                    1 Reply Last reply Reply Quote 1
                    • GertjanG
                      Gertjan @3aandl
                      last edited by

                      @3aandl

                      I just installed _17 and that one is fine.

                      No "help me" PM's please. Use the forum, the community will thank you.
                      Edit : and where are the logs ??

                      1 Reply Last reply Reply Quote 1
                      • D
                        deepakm
                        last edited by

                        I face same problem after upgrading . But i resolved it.

                        First Login by ssh then enter shell (8). Then enter cd /usr/local/www/ directory and remove pfblockerng folder . Then make new directory pfblockerng and give directory root:wheel permission. After this process run this cmd

                        For pfsense plus (

                        curl -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://gist.githubusercontent.com/BBcan177/72d559647564acc6a0b8353b72a40049/raw"
                        curl -o /usr/local/pkg/pfblockerng/pfblockerng.sh "https://gist.githubusercontent.com/BBcan177/abdeba2d1ee055efe3d5c23ab558c40d/raw"
                        curl -o /usr/local/www/pfblockerng/pfblockerng.php "https://gist.githubusercontent.com/BBcan177/8d67e132ad16b895b5dd8996c22359e3/raw"
                        curl -o /usr/local/www/pfblockerng/pfblockerng_ip.php "https://gist.githubusercontent.com/BBcan177/ff538442a2e7cf78a9f24119b70f575a/raw"
                        curl -o /usr/local/www/pfblockerng/pfblockerng_alerts.php "https://gist.githubusercontent.com/BBcan177/f2873a9b59bb491f5af6802c72807110/raw") and

                        for pfsense CE ( curl -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://gist.githubusercontent.com/BBcan177/e0347961852bfed16408bae2b475c36a/raw"
                        curl -o /usr/local/pkg/pfblockerng/pfblockerng.sh "https://gist.githubusercontent.com/BBcan177/abdeba2d1ee055efe3d5c23ab558c40d/raw"
                        curl -o /usr/local/www/pfblockerng/pfblockerng.php "https://gist.githubusercontent.com/BBcan177/8d67e132ad16b895b5dd8996c22359e3/raw"
                        curl -o /usr/local/www/pfblockerng/pfblockerng_ip.php "https://gist.githubusercontent.com/BBcan177/ff538442a2e7cf78a9f24119b70f575a/raw"
                        curl -o /usr/local/www/pfblockerng/pfblockerng_alerts.php "https://gist.githubusercontent.com/BBcan177/5a9a16698410c1171ddbb74df1007c7b/raw"
                        curl -o /usr/local/pkg/pfblockerng/pfblockerng_extra.inc "https://gist.githubusercontent.com/BBcan177/324e291bdf7636d34d274cc26490e764/raw")

                        After this exit run 16 and 11 . After this process your dashboard will be work.

                        1 Reply Last reply Reply Quote 0
                        • D
                          dotsch @Spacey 0
                          last edited by

                          Thank you very much for the work around.
                          Had the same issue on 2.7.2 and it fixed it.

                          1 Reply Last reply Reply Quote 0
                          • R
                            revengineer
                            last edited by

                            I confirm, _17 went well and resolves the issue. Thank you!

                            UnoptanioU 1 Reply Last reply Reply Quote 1
                            • UnoptanioU
                              Unoptanio @revengineer
                              last edited by Unoptanio

                              @revengineer

                              with version _17 now everything is ok we are online again

                              This problem made me discover the usefulness of boot environments

                              Active one time and reboot

                              6db665ce-712a-49eb-81d6-a0cc98d8b901-image.png

                              pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
                              CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
                              n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

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

                                Is the update only available with the -devel package or will pfBlockerNG 3.2.0_8 also receive the update to _17?

                                pfSense Gold subscription

                                GertjanG J 2 Replies Last reply Reply Quote 0
                                • GertjanG
                                  Gertjan @slu
                                  last edited by

                                  @slu

                                  AFAIK :
                                  The _10 or non-devel remains stable and the same.
                                  The devel version was upgraded, to see if all was ok and so on. If that was the case, the non devel would also be updated afterwards.
                                  Remember : "devel" is bleeding edge technology. And sometimes there is progress, sometimes there is blood.

                                  No "help me" PM's please. Use the forum, the community will thank you.
                                  Edit : and where are the logs ??

                                  1 Reply Last reply Reply Quote 2
                                  • J
                                    jrey @slu
                                    last edited by

                                    @slu

                                    Just wait on a production system. there will be more. _17 still has "show stoppers"

                                    yes you can "get around" some of them, but not all.
                                    production wait.
                                    installing and package testing -devel

                                    1 Reply Last reply Reply Quote 0
                                    • J jrey referenced this topic on
                                    • S
                                      SteveITS Galactic Empire @BBcan177
                                      last edited by

                                      To clarify for anyone finding this thread and looking for IPInfo ASN fields:

                                      On 24.11, pfBlockerNG 3.2.0_16 does not include the IPInfo ASN token fields.

                                      pfBlockerNG-devel 3.2.1_20 does.

                                      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!

                                      GertjanG 1 Reply Last reply Reply Quote 0
                                      • GertjanG
                                        Gertjan @SteveITS
                                        last edited by Gertjan

                                        @SteveITS said in pfBlockerNG-devel v3.2.0_15:

                                        On 24.11, pfBlockerNG 3.2.0_16 does not include the IPInfo ASN token fields.

                                        pfBlockerNG-devel 3.2.1_20 does.

                                        Totally agree with this. For me, this implies :

                                        Use pfBlockerNG-devel 3.2.1_20 - this means the latest version and thus I have to to deal with current, new issues, the old ones are gone. Chances are great the forum has very actual info and probably even a solution right now for these new issues.
                                        When we use pfBlockerNG 3.2.0_16, will have to deal with the issues already known and solved.

                                        So, what will it be ? _20 or version _16 ?

                                        For me, the choice is a simple one. I've been using the 'devel' version and never regretted it 😊

                                        No "help me" PM's please. Use the forum, the community will thank you.
                                        Edit : and where are the logs ??

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