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

    PfBlockerNG v2.0 w/DNSBL

    Scheduled Pinned Locked Moved pfBlockerNG
    1.1k Posts 192 Posters 1.7m 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.
    • F
      Fesoj
      last edited by

      Hi!

      I read the info about 2.3 and I shall update asap. For the time being I'd like to update to 2.0.5 on an older 2.2. box. The installation aborted with the message

      Downloading https://files.pfsense.org/packages/10/All/pfblockerng-1.6.6-amd64.pbi ...  could not download from there
      

      It seems that the .pbi file is missing.  Did someone else run into the same problem?

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

        @Fesoj:

        Hi!

        I read the info about 2.3 and I shall update asap. For the time being I'd like to update to 2.0.5 on an older 2.2. box. The installation aborted with the message

        Downloading https://files.pfsense.org/packages/10/All/pfblockerng-1.6.6-amd64.pbi ...  could not download from there
        

        It seems that the .pbi file is missing.  Did someone else run into the same problem?

        I can download the file from the shell without issue:

        fetch -o /tmp/pfblockerng-1.6.6-amd64.pbi https://files.pfsense.org/packages/10/All/pfblockerng-1.6.6-amd64.pbi
        

        "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
        • F
          Fesoj
          last edited by

          This time the file was found.

          1 Reply Last reply Reply Quote 0
          • A
            adx442
            last edited by

            Haven't had issues with pfBlockerNG on 2.2.x, but I've upgraded to 2.3RC (and I've tried uninstalling/reinstalling pfB), but I get this error and a pfSense crash report every time I click the Alerts tab under pfBlockerNG's section:

            Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72 bytes) in /usr/local/www/pfblockerng/pfblockerng_alerts.php on line 581 Call Stack: 0.0141 232168 1. {main}() /usr/local/www/pfblockerng/pfblockerng_alerts.php:0 1.4219 2882400 2. conv_log_filter_lite() /usr/local/www/pfblockerng/pfblockerng_alerts.php:362 1.4220 2883016 3. exec() /usr/local/www/pfblockerng/pfblockerng_alerts.php:581 PHP ERROR: Type: 1, File: /usr/local/www/pfblockerng/pfblockerng_alerts.php, Line: 581, Message: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72 bytes)

            This is on a Netgate C2758 box with 8GB of RAM and a small SSD with plenty of space, so this error doesn't make much sense to me.  Is there a hard-set limit somewhere that I can adjust upwards?

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

              Hi adx442,

              The Alerts tab reads the pfSense Firewall logs. How many log entries do you have defined in the syslog settings? Also try to clear the firewall log and see if the error returns. The memory issue is related to PHP and not the hardware itself.

              "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
              • A
                adx442
                last edited by

                Yup, I'd already increased PHP's memory limit to 512M.  Turns out, the syslog size was a little too large for even that amount of memory, cutting it in half and clearing the logs did fix the behavior.

                Sorry, the only place I'd been seeing this issue exposed was in pfBlockerNG, though it was unrelated in the end.

                1 Reply Last reply Reply Quote 0
                • W
                  Wolf666
                  last edited by

                  I noted that each time I update pfSense 2.3 build, after reboot or no, DNSBL lists are not correctly loaded, in fact the widget shows 0 ips. I have to manually ask for reload to get list loaded and blocking feature to work again.

                  Modem Draytek Vigor 130
                  pfSense 2.4 Supermicro A1SRi-2558 - 8GB ECC RAM - Intel S3500 SSD 80GB - M350 Case
                  Switch Cisco SG350-10
                  AP Netgear R7000 (Stock FW)
                  HTPC Intel NUC5i3RYH
                  NAS Synology DS1515+
                  NAS Synology DS213+

                  1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User
                    last edited by

                    Same here as noted by Wolf666. Below the link to a related or not issue :o with Unbound not starting properly after any reboot.

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

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

                      @Wolf666:

                      I noted that each time I update pfSense 2.3 build, after reboot or no, DNSBL lists are not correctly loaded, in fact the widget shows 0 ips. I have to manually ask for reload to get list loaded and blocking feature to work again.

                      @webtyro:

                      Same here as noted by Wolf666.

                      Thanks for the report…

                      If you are able to modify a file, please edit:    /usr/local/pkg/pfblockerng/pfblockerng.inc

                      In 2.3 - Line : 3149
                      https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG/files/usr/local/pkg/pfblockerng/pfblockerng.inc#L3149

                      In 2.2.x - Line: 3156
                      https://github.com/pfsense/pfsense-packages/blob/master/config/pfblockerng/pfblockerng.inc#L3156

                      and edit the line:

                      if (empty($lists_dnsbl_all)) {

                      to

                      if (empty($lists_dnsbl_all) && !$pfb['save']) {

                      First make sure that the widget doesn't show the DNSBL count as "0" (Run a force reload if its "0"), then reboot and ensure that post-reboot that the widget DNSBL count is accurate…

                      Post back if this fixes this issue...

                      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/

                      1 Reply Last reply Reply Quote 0
                      • T
                        turker
                        last edited by

                        @BBcan177:

                        and edit the line:

                        if (empty($lists_dnsbl_all)) {

                        to

                        if (empty($lists_dnsbl_all) && !$pfb['save']) {

                        First make sure that the widget doesn't show the DNSBL count as "0" (Run a force reload if its "0"), then reboot and ensure that post-reboot that the widget DNSBL count is accurate…

                        Post back if this fixes this issue...

                        Thanks!

                        Fix my problem. Thanks BBcan177.

                        1 Reply Last reply Reply Quote 0
                        • W
                          Wolf666
                          last edited by

                          Fix mine also.

                          Modem Draytek Vigor 130
                          pfSense 2.4 Supermicro A1SRi-2558 - 8GB ECC RAM - Intel S3500 SSD 80GB - M350 Case
                          Switch Cisco SG350-10
                          AP Netgear R7000 (Stock FW)
                          HTPC Intel NUC5i3RYH
                          NAS Synology DS1515+
                          NAS Synology DS213+

                          1 Reply Last reply Reply Quote 0
                          • ?
                            A Former User
                            last edited by

                            @BBcan177
                            That did the trick for mine also. Thank you.

                            1 Reply Last reply Reply Quote 0
                            • N
                              nightanole
                              last edited by

                              Semi complete n00b here.  I got it up and running with just dnsbl.  However it just stops after a few hours and lets everything through.  Is there something i can check?  I cant see any errors being thrown in the logs, cron jobs are doing things etc every hour.

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

                                Ensure that your LAN devices have their DNS settings set to only pfSense. If you ping the DNSBL VIP does it resolve? If you browse the the DNSBL VIP do you get the 1x1?

                                "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
                                • N
                                  nightanole
                                  last edited by

                                  i can ping the VIP from my 192.1.6.2.xxx to the VIP http://10.10.10.1/.

                                  If i load up the web page its blank.

                                  Not seeing anything about a gif.

                                  The only hint is <title>10.10.10.1 (1×1)</title>

                                  This happens if it is blocking correctly or incorrectly.

                                  It seems that everything works till the first cron job.  After that if i want it to work i have to force update till the next cron job.

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

                                    Can you follow the instructions in this post:

                                    https://forum.pfsense.org/index.php?topic=102470.msg607864#msg607864

                                    "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
                                    • BBcan177B
                                      BBcan177 Moderator
                                      last edited by

                                      I have posted PR #1247, pfBlockerNG v2.0.6 (for pfSense v2.2.x)
                                        and
                                      I have posted PR #94,    pfBlockerNG v2.0.9 (for pfSense v2.3)

                                      Hopefully the Devs merge this asap, to fix the recent issue being reported…

                                      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/

                                      1 Reply Last reply Reply Quote 0
                                      • N
                                        nightanole
                                        last edited by

                                        @BBcan177:

                                        Can you follow the instructions in this post:

                                        https://forum.pfsense.org/index.php?topic=102470.msg607864#msg607864

                                        Thank you.  It has been up for 3 cron jobs and is still working.

                                        After the first reboot  after the patch i did have to force update to get this to work the first time:
                                        ===[  DNSBL Process  ]================================================
                                        Missing DNSBL stats and/or Unbound DNSBL conf file - Rebuilding

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

                                          @BBcan177:

                                          I have posted PR #1247, pfBlockerNG v2.0.6 (for pfSense v2.2.x)
                                            and
                                          I have posted PR #94,    pfBlockerNG v2.0.9 (for pfSense v2.3)

                                          Hopefully the Devs merge this asap, to fix the recent issue being reported…

                                          Thanks!

                                          FYI - Both Pull Requests have been merged…

                                          "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
                                            mgchristensen
                                            last edited by

                                            Hello all,

                                            pfSense noob here.  Using pfSense since November 2015.  Full install of pfSense on SuperMicro A1SAi-27f0F, 16GM RAM.  I am having a strange problem, and am not sure what I did.  I was happily using pfBlocker_NG with DNSBL.  I upgraded pfBNG from 2.04 to 2.05 four days ago.  When I reboot, the LAN interface is now assigned the DNSBL Virtual IP (10.10.10.1) and not the 192.168.1.1 IP as specified under Interfaces: LAN.  I have to manually "2) Set interface(s) IP address" in a ssh session, before I can log in to the GUI and disable DNSBL.  Reboot, and the LAN gets the 192.168.1.1 IP. Same with 2.05 to 2.06.  Did not have this issue with version 2.04.  I would rather not wipe the box and start over, if someone might point me in another direction.  Thanks in advance.

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