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

    PfSense-pkg-pfBlockerNG-2.0.17 breaks package manager - need help

    Scheduled Pinned Locked Moved pfBlockerNG
    19 Posts 5 Posters 4.9k 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.
    • D
      dsefcik
      last edited by

      The only block I enabled was the china country set but when I realized the Dashboard status was broken I disabled pfBlocker and there was no change. Then I noticed package manager was also broken so I could not remove the package so then I removed it manually but that did not change the package manager or Dashboard status. I also verified all of the firewall rules were removed.

      Yes, ping to pfsense works

      /root: ping pkg.pfsense.org
      PING pkg.pfsense.org (162.208.119.39): 56 data bytes
      64 bytes from 162.208.119.39: icmp_seq=0 ttl=53 time=70.019 ms
      64 bytes from 162.208.119.39: icmp_seq=1 ttl=53 time=70.027 ms
      64 bytes from 162.208.119.39: icmp_seq=2 ttl=53 time=70.065 ms
      
      1 Reply Last reply Reply Quote 0
      • BBcan177B
        BBcan177 Moderator
        last edited by

        It's probably a coincidence that the pkg/dashboard issue came about at the same time? Check the system.log for any other clues. If the pkg is Uninstalled, there are no firewall rule from the pkg and DNS if functioning then it seems to be something else? Maybe try a reboot?

        "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/

        1 Reply Last reply Reply Quote 0
        • D
          dsefcik
          last edited by

          Nothing in logs, reboot did not help, other pfsenses boxes work fine.
          I am rolling back VM snapshots but would like to resolve this as I want to use pfBlocker.

          TIA

          1 Reply Last reply Reply Quote 0
          • D
            dsefcik
            last edited by

            Just rolled back both machines with VM snapshots and everything is back to normal so something with that package made 2 systems stop talking to pfsense package systems(?). Unless you have any other suggestions all I can try next would be to create a test system or roll back the snapshots to the broken version again and try some other suggestions.

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

              I have not seen this issue myself. But I noticed the following in reddit:

              https://js4.red/r/PFSENSE/comments/4v3jxp/unable_to_view_packages_system_updates_after/

              I don't believe the issue to be with the pkg.

              "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/

              1 Reply Last reply Reply Quote 0
              • D
                dsefcik
                last edited by

                Yep, I saw that also..thanks.
                I will have to build a test system.

                1 Reply Last reply Reply Quote 0
                • D
                  dsefcik
                  last edited by

                  I think pkg manager is broken, I installed rsync and it also had the same effect, upgrading to 2.3.2 in the console fixed the broken pkg manager but I still need to test pfBlocker but suspect it will be fine.

                  https://forum.pfsense.org/index.php?topic=115777.0

                  –

                  1 Reply Last reply Reply Quote 0
                  • RonpfSR
                    RonpfS
                    last edited by

                    https://forum.pfsense.org/index.php?topic=116223.0

                    2.4.5-RELEASE-p1 (amd64)
                    Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                    Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                    1 Reply Last reply Reply Quote 0
                    • L
                      larsnextware
                      last edited by

                      Hi,

                      Just installed 2.3.2 on a 2.3.1p5 with pfBlocker and after that I'm unable to get pfBlocker going.

                      I uninstalled pfBlocker (when running 2.3.2) and then reinstalled it again, but no pfBlocker shows up in the menu.

                      Anyone else encountered this?

                      Best regards,
                      Lars

                      1 Reply Last reply Reply Quote 0
                      • RonpfSR
                        RonpfS
                        last edited by

                        @RonpfS:

                        Well during installation pfBlockerNG download the MaxMind GeoIP database … it probably crashes and the installation doesn't complete.  :o

                        2.4.5-RELEASE-p1 (amd64)
                        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                        1 Reply Last reply Reply Quote 0
                        • RonpfSR
                          RonpfS
                          last edited by

                          @larsnextware:

                          Hi,

                          Just installed 2.3.2 on a 2.3.1p5 with pfBlocker and after that I'm unable to get pfBlocker going.

                          I uninstalled pfBlocker (when running 2.3.2) and then reinstalled it again, but no pfBlocker shows up in the menu.

                          Anyone else encountered this?

                          Best regards,
                          Lars

                          Fix removed because it doesn't seems to be related to GeoIP issue

                          2.4.5-RELEASE-p1 (amd64)
                          Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                          Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                          1 Reply Last reply Reply Quote 0
                          • RonpfSR
                            RonpfS
                            last edited by

                            You may need to increase it to 400M or 500M if this fails

                            2.4.5-RELEASE-p1 (amd64)
                            Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                            Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                            1 Reply Last reply Reply Quote 0
                            • RonpfSR
                              RonpfS
                              last edited by

                              Another fix removed. Until we can pinpoint the issue.

                              2.4.5-RELEASE-p1 (amd64)
                              Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                              Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                              1 Reply Last reply Reply Quote 0
                              • RonpfSR
                                RonpfS
                                last edited by

                                removed

                                2.4.5-RELEASE-p1 (amd64)
                                Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                                Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                                1 Reply Last reply Reply Quote 0
                                • RonpfSR
                                  RonpfS
                                  last edited by

                                  So it looks that after a reboot the installation went fine without fixing any file on his system.

                                  2.4.5-RELEASE-p1 (amd64)
                                  Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                                  Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mdima
                                    last edited by

                                    Same issue here, same fix. After uninstalling, rebooting and reinstalling everything worked (2.3.2-RELEASE (amd64))

                                    UPDATE: That was valid only on one box, on the other it is still not present :S
                                    UPDATE2: I traced this entry as error while reinstalling:

                                    PHP ERROR: Type: 1, File: /usr/local/www/pfblockerng/pfblockerng.php, Line: 728, Message: Allowed memory size of 134217728 bytes exhausted (tried to allocate 36 bytes)pkg: POST-INSTALL script failed
                                    
                                    

                                    UPDATE3: Ok, got to the root of the problem. During the upgrade done yesterday (2.2.6 to 2.3.1 and immediately to 2.3.2) one box was changing architecture, from AMD64 to i386 :S
                                    I will have to perform a fresh install then restore the config.

                                    but that's wired…

                                    1 Reply Last reply Reply Quote 0
                                    • D
                                      dsefcik
                                      last edited by

                                      @dsefcik:

                                      I think pkg manager is broken, I installed rsync and it also had the same effect, upgrading to 2.3.2 in the console fixed the broken pkg manager but I still need to test pfBlocker but suspect it will be fine.

                                      https://forum.pfsense.org/index.php?topic=115777.0

                                      –

                                      Just an update, after upgrading both systems to 2.3.2 I was able to install pfBlocker fine and it seems to work as expected, thank you for your help.

                                      1 Reply Last reply Reply Quote 0
                                      • First post
                                        Last post
                                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.