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

    Removing pfblocker

    Scheduled Pinned Locked Moved pfBlockerNG
    31 Posts 15 Posters 17.2k 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
      Seb
      last edited by

      P.S. The script removed nothing as far as I could tell: the pfBlocker rules were still present and the menu entry was still present.

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

        It won't remove the rules but it should remove the menu entry. Is this a full install version of pfSense. Might need to put the system into RW mode to save the changes if it's a nano/flash type version.

        "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
        • M
          mloiterman
          last edited by

          greping the config file still shows 'pfblockersync'.  Should that be there?

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

            @mloiterman:

            greping the config file still shows 'pfblockersync'.  Should that be there?

            Thanks for pointing that out. I can't edit my original post, but please edit the script to include "pfblockersync" as follows:

            Original

            $removal = array("pfblocker", "pfblockerlists", "pfblockerafrica", "pfblockerantartica", "pfblockerasia", "pfblockereurope", "pfblockernorthamerica", "pfblockeroceania", "pfblockersouthamerica", "pfblockertopspammers");

            New

            $removal = array("pfblocker", "pfblockerlists", "pfblockerafrica", "pfblockerantartica", "pfblockerasia", "pfblockereurope", "pfblockernorthamerica", "pfblockeroceania", "pfblockersouthamerica", "pfblockertopspammers", "pfblockersync");

            "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
            • G
              glenewhittenberggmail.co
              last edited by

              script saved me. upgraded from 2.2.4 to 2.3.1 and pfblocker broke. Tried remove and reinstall no go. was able to get to router but not out to internet. ran script, rebooted, and all my problems are gone. Thanks!

              1 Reply Last reply Reply Quote 0
              • yuljkY
                yuljk
                last edited by

                Just tried running this - after copying the script to my pfsense VM.

                I ran the script from Chrome and it just outputs 'Removing pfBlocker from the pfSense Configuration file'

                Where exactly am I executing the script from?

                Thanks

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

                  The script is outdated.

                  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

                    To install or re-install pfBlockerNG 2.1.1_2
                    https://forum.pfsense.org/index.php?topic=102470.msg647719#msg647719

                    Then you can install or re-install the pfBlockerNG 2.1.1_2.
                    The install should update the MaxMind (this take 5+ minutes) and proceed to completion.

                    Then you can remove the package

                    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
                    • yuljkY
                      yuljk
                      last edited by

                      Many thanks for the new fix.

                      I have attempted a new install after modifying config.inc.  However the pfBlockerng entry under my firewall menu is not visible.

                      Installation log:-

                      Installing pfSense-pkg-pfBlockerNG…
                      Updating pfSense-core repository catalogue...
                      pfSense-core repository is up-to-date.
                      Updating pfSense repository catalogue...
                      pfSense repository is up-to-date.
                      All repositories are up-to-date.
                      Checking integrity... done (0 conflicting)
                      The following 6 package(s) will be affected (of 0 checked):

                      New packages to be INSTALLED:
                      pfSense-pkg-pfBlockerNG: 2.1.1_2 [pfSense]
                      whois: 5.1.5 [pfSense]
                      GeoIP: 1.6.9 [pfSense]
                      lighttpd: 1.4.39_1 [pfSense]
                      grepcidr: 2.0 [pfSense]
                      aggregate: 1.6_1 [pfSense]

                      Number of packages to be installed: 6

                      The process will require 2 MiB more space.
                      [1/6] Installing whois-5.1.5…
                      [1/6] Extracting whois-5.1.5: …....... done
                      [2/6] Installing GeoIP-1.6.9…
                      [2/6] Extracting GeoIP-1.6.9: …....... done
                      [3/6] Installing lighttpd-1.4.39_1…
                      [3/6] Extracting lighttpd-1.4.39_1: …....... done
                      [4/6] Installing grepcidr-2.0…
                      [4/6] Extracting grepcidr-2.0: ….. done
                      [5/6] Installing aggregate-1.6_1…
                      [5/6] Extracting aggregate-1.6_1: …. done
                      [6/6] Installing pfSense-pkg-pfBlockerNG-2.1.1_2…
                      [6/6] Extracting pfSense-pkg-pfBlockerNG-2.1.1_2: …....... done
                      Saving updated package information...
                      done.
                      Loading package configuration... done.
                      Configuring package components...
                      Loading package instructions...
                      Custom commands...
                      Executing custom_php_install_command()...
                      MaxMind GeoIP databases previously downloaded.
                      Adding pfBlockerNG Widget to the Dashboard... done.
                      Remove any existing and create link for DNSBL lighttpd executable... done.
                      Creating DNSBL web server start-up script... done.
                      Upgrading Adv. Inbound firewall rule settings ... no changes required ... done.
                      Custom commands completed ... done.
                      Executing custom_php_resync_config_command()...pkg: POST-INSTALL script failed
                      Message from GeoIP-1.6.9:
                      GeoIP does not ship with the actual data files. You must download
                      them yourself! Please run:

                      /usr/local/bin/geoipupdate.sh

                      Cleaning up cache... done.
                      Success

                      Immediately after install I get a crash report:-

                      Crash report begins.  Anonymous machine information:

                      amd64
                      10.3-RELEASE-p5
                      FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 13:29:35 CDT 2016    root@ce23-amd64-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense

                      Crash report details:

                      PHP Errors:
                      [14-Aug-2016 14:42:20 Europe/London] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 72 bytes) in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3874
                      [14-Aug-2016 14:42:20 Europe/London] PHP Stack trace:
                      [14-Aug-2016 14:42:20 Europe/London] PHP  1. {main}() /etc/rc.start_packages:0
                      [14-Aug-2016 14:42:20 Europe/London] PHP  2. sync_package() /etc/rc.start_packages:90
                      [14-Aug-2016 14:42:20 Europe/London] PHP  3. eval() /etc/inc/pkg-utils.inc:631
                      [14-Aug-2016 14:42:20 Europe/London] PHP  4. sync_package_pfblockerng() /etc/inc/pkg-utils.inc(631) : eval()'d code:3
                      [14-Aug-2016 14:42:20 Europe/London] PHP  5. file() /usr/local/pkg/pfblockerng/pfblockerng.inc:3874

                      Pfsense 2.3.2 running on ESXi 6 VM with 2GB RAM and 4vCPUs

                      Many thanks

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

                        
                        // Set memory limit to 512M on amd64.
                        if ($ARCH == "amd64") {
                        	ini_set("memory_limit", "512M");
                        } else {
                        	ini_set("memory_limit", "256M");
                        }
                        
                        

                        You are using the AMD64 version, try to increase to 768M:

                        
                        if ($ARCH == "amd64") {
                        	ini_set("memory_limit", "768M");
                        } else {
                        	ini_set("memory_limit", "256M");
                        }
                        
                        

                        Or wait until BBCan releases the fix

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

                          To increase memory_limit over 512M you also need to fix /usr/local/etc/php.ini, /etc/rc.php_ini_setup

                          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
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.