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

    pfBlockerNG-devel feedback

    Scheduled Pinned Locked Moved pfBlockerNG
    102 Posts 26 Posters 100.5k 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.
    • H
      Hugovsky
      last edited by Hugovsky

      Also noted that pfBlocker doesn't log my direct connection to 10.10.10.1. It used to.

      1 Reply Last reply Reply Quote 0
      • VeldkornetV
        Veldkornet @BBcan177
        last edited by

        @bbcan177 said in pfBlockerNG-devel feedback:

        @veldkornet said in pfBlockerNG-devel feedback:

        On my dashboard, DNSBL always has a yellow icon and says
        DNSBL is out of sync. Perform a force reload to correct.

        Although I’ve already done a force reload a few times...
        Also, unrelated to the above, would it be possible to allow the ability to choose your own certificate for DNSBL so that you don’t get certificate errors for the https page?

        For the Sync issue: Typically this is caused by having multiple feeds with the same "Header/Label" name. Every Header needs to be unique. Also can be caused if you have a duplicated Feed.

        For the Certificate errors, you can fix this in pfBlockerNG-devel, see here:
        https://forum.netgate.com/topic/136302/is-hiding-dnsbl-alerts-without-whitlisting-possible

        For the sync issue, I went through all the feeds but I didn’t notice any duplicates in Feed or tag... is it possible that there’s a duplicate from the custom feed and the Easylist Shalla (for example)? Or is there another way to track it down?

        FYI, I’m using most of these: https://firebog.net

        BBcan177B RonpfSR 2 Replies Last reply Reply Quote 0
        • BBcan177B
          BBcan177 Moderator @Veldkornet
          last edited by

          @veldkornet

          See the last part of the pfblockerng.log which will summarize all headers.

          Failing that, uncheck "keep settings" and hit "save" in the general tab which will clear all downloaded files.

          Follow that by rechecking "keep settings", save and a Force update.

          "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
          • RonpfSR
            RonpfS @Veldkornet
            last edited by

            @veldkornet Look at https://forum.netgate.com/topic/130361/pfblockerng-devel-2-1-2/14

            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 1
            • newyork10023N
              newyork10023 @BBcan177
              last edited by newyork10023

              @bbcan177 I am unclear as to the correct setting on Services -> DNS Resolver -> General Settings under Network Interfaces: it specifies "[IP Address] (pfB DNSBL - DO NOT EDIT)". Well, it got edited (and, indeed, again now). Should this entry be selected (i.e., highlighted/checked) or not? In general, do I want all local internal interfaces checked here including the pfB DNSBL one? Perhaps, the entry could be more "descriptive" than "Do not edit" (e.g., "Select to enable pfB DNSBL").

              1 Reply Last reply Reply Quote 0
              • VeldkornetV
                Veldkornet
                last edited by

                Speaking of the DNS Resolver, under the custom options, the following:

                include: /var/unbound/pfb_dnsbl.*conf

                As that looked wrong, I changed it to:

                include: /var/unbound/pfb_dnsbl*.conf

                Right, so now it works properly and picks up all of the config files, but now because of this, I get the following error:

                The following input errors were detected:

    The generated config file cannot be parsed by unbound. Please correct the following errors:
    /var/unbound/pfb_dnsbl_lighty.conf:4: error: unknown keyword 'server.tag'
    /var/unbound/pfb_dnsbl_lighty.conf:4: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:4: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:4: error: unknown keyword 'pfBlockerNG'
    /var/unbound/pfb_dnsbl_lighty.conf:4: error: unknown keyword 'DNSBL'
    /var/unbound/pfb_dnsbl_lighty.conf:4: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:5: error: unknown keyword 'server.bind'
    /var/unbound/pfb_dnsbl_lighty.conf:5: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:5: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:5: error: unknown keyword '0.0.0.0'
    /var/unbound/pfb_dnsbl_lighty.conf:5: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:6: error: unknown keyword 'server.port'
    /var/unbound/pfb_dnsbl_lighty.conf:6: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:6: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:6: error: unknown keyword '8082'
    /var/unbound/pfb_dnsbl_lighty.conf:6: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:7: error: unknown keyword 'server.event-handler'
    /var/unbound/pfb_dnsbl_lighty.conf:7: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:7: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:7: error: unknown keyword 'freebsd-kqueue'
    /var/unbound/pfb_dnsbl_lighty.conf:7: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:8: error: unknown keyword 'server.network-backend'
    /var/unbound/pfb_dnsbl_lighty.conf:8: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:8: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:8: error: unknown keyword 'freebsd-sendfile'
    /var/unbound/pfb_dnsbl_lighty.conf:8: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:9: error: unknown keyword 'server.dir-listing'
    /var/unbound/pfb_dnsbl_lighty.conf:9: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:9: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:9: error: unknown keyword 'disable'
    /var/unbound/pfb_dnsbl_lighty.conf:9: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:10: error: unknown keyword 'server.document-root'
    /var/unbound/pfb_dnsbl_lighty.conf:10: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:10: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:10: error: unknown keyword '/usr/local/www/pfblockerng/www/'
    /var/unbound/pfb_dnsbl_lighty.conf:10: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:11: error: unknown keyword 'server.errorlog'
    /var/unbound/pfb_dnsbl_lighty.conf:11: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:11: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:11: error: unknown keyword '|/usr/local/bin/php'
    /var/unbound/pfb_dnsbl_lighty.conf:11: error: unknown keyword '-f'
    /var/unbound/pfb_dnsbl_lighty.conf:11: error: unknown keyword '/usr/local/pkg/pfblockerng/pfblockerng.inc'
    /var/unbound/pfb_dnsbl_lighty.conf:11: error: unknown keyword 'dnsbl'
    /var/unbound/pfb_dnsbl_lighty.conf:11: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:12: error: unknown keyword 'server.pid-file'
    /var/unbound/pfb_dnsbl_lighty.conf:12: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:12: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:12: error: unknown keyword '/var/run/dnsbl.pid'
    /var/unbound/pfb_dnsbl_lighty.conf:12: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword 'server.modules'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword '('
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword 'mod_access'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword ','
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword 'mod_accesslog'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword ','
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword 'mod_fastcgi'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword ','
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword 'mod_rewrite'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword ','
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword 'mod_openssl'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:13: error: unknown keyword ')'
    /var/unbound/pfb_dnsbl_lighty.conf:14: error: unknown keyword 'server.indexfiles'
    /var/unbound/pfb_dnsbl_lighty.conf:14: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:14: error: unknown keyword '('
    /var/unbound/pfb_dnsbl_lighty.conf:14: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:14: error: unknown keyword 'index.php'
    /var/unbound/pfb_dnsbl_lighty.conf:14: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:14: error: unknown keyword ')'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: unknown keyword 'mimetype.assign'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: unknown keyword '('
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: unknown keyword '.html'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: unknown keyword '=>'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: unknown keyword 'text/html'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: unknown keyword ','
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: unknown keyword '.gif'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: unknown keyword '=>'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: unknown keyword 'image/gif'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:15: error: unknown keyword ')'
    /var/unbound/pfb_dnsbl_lighty.conf:16: error: unknown keyword 'url.access-deny'
    /var/unbound/pfb_dnsbl_lighty.conf:16: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:16: error: unknown keyword '('
    /var/unbound/pfb_dnsbl_lighty.conf:16: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:16: error: unknown keyword '~'
    /var/unbound/pfb_dnsbl_lighty.conf:16: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:16: error: unknown keyword ','
    /var/unbound/pfb_dnsbl_lighty.conf:16: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:16: error: unknown keyword '.inc'
    /var/unbound/pfb_dnsbl_lighty.conf:16: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:16: error: unknown keyword ')'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword 'fastcgi.server'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword '('
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword '.php'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword '=>'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword '('
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword 'localhost'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword '=>'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword '('
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword 'socket'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword '=>'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword '/var/run/php-fpm.socket'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword ','
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword 'broken-scriptfilename'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword '=>'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword 'enable'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword ')'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword ')'
    /var/unbound/pfb_dnsbl_lighty.conf:17: error: unknown keyword ')'
    /var/unbound/pfb_dnsbl_lighty.conf:19: error: unknown keyword 'debug.log-condition-handling'
    /var/unbound/pfb_dnsbl_lighty.conf:19: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:19: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:19: error: unknown keyword 'enable'
    /var/unbound/pfb_dnsbl_lighty.conf:19: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:20: error: unknown keyword 'accesslog.use-syslog'
    /var/unbound/pfb_dnsbl_lighty.conf:20: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:20: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:20: error: unknown keyword 'disable'
    /var/unbound/pfb_dnsbl_lighty.conf:20: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:21: error: unknown keyword 'accesslog.format'
    /var/unbound/pfb_dnsbl_lighty.conf:21: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:21: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:21: error: unknown keyword 'INDEX!%r!%V!%h!%{Referer}i'
    /var/unbound/pfb_dnsbl_lighty.conf:21: error: unknown keyword '*'
    /var/unbound/pfb_dnsbl_lighty.conf:21: error: unknown keyword '%r'
    /var/unbound/pfb_dnsbl_lighty.conf:21: error: unknown keyword '*'
    /var/unbound/pfb_dnsbl_lighty.conf:21: error: unknown keyword '%{User-Agent}i'
    /var/unbound/pfb_dnsbl_lighty.conf:21: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:22: error: unknown keyword 'accesslog.filename'
    /var/unbound/pfb_dnsbl_lighty.conf:22: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:22: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:22: error: unknown keyword '|/usr/local/bin/php'
    /var/unbound/pfb_dnsbl_lighty.conf:22: error: unknown keyword '-f'
    /var/unbound/pfb_dnsbl_lighty.conf:22: error: unknown keyword '/usr/local/pkg/pfblockerng/pfblockerng.inc'
    /var/unbound/pfb_dnsbl_lighty.conf:22: error: unknown keyword 'index'
    /var/unbound/pfb_dnsbl_lighty.conf:22: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:24: error: unknown keyword '$HTTP['
    /var/unbound/pfb_dnsbl_lighty.conf:24: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:24: error: unknown keyword 'scheme'
    /var/unbound/pfb_dnsbl_lighty.conf:24: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:24: error: unknown keyword ']'
    /var/unbound/pfb_dnsbl_lighty.conf:24: error: unknown keyword '=='
    /var/unbound/pfb_dnsbl_lighty.conf:24: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:24: error: unknown keyword 'http'
    /var/unbound/pfb_dnsbl_lighty.conf:24: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:24: error: unknown keyword '{'
    /var/unbound/pfb_dnsbl_lighty.conf:25: error: unknown keyword 'url.rewrite-once'
    /var/unbound/pfb_dnsbl_lighty.conf:25: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:25: error: unknown keyword '('
    /var/unbound/pfb_dnsbl_lighty.conf:25: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:25: error: unknown keyword '.*'
    /var/unbound/pfb_dnsbl_lighty.conf:25: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:25: error: unknown keyword '=>'
    /var/unbound/pfb_dnsbl_lighty.conf:25: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:25: error: unknown keyword 'index.php'
    /var/unbound/pfb_dnsbl_lighty.conf:25: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:25: error: unknown keyword ')'
    /var/unbound/pfb_dnsbl_lighty.conf:26: error: unknown keyword '}'
    /var/unbound/pfb_dnsbl_lighty.conf:28: error: unknown keyword '$HTTP['
    /var/unbound/pfb_dnsbl_lighty.conf:28: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:28: error: unknown keyword 'remoteip'
    /var/unbound/pfb_dnsbl_lighty.conf:28: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:28: error: unknown keyword ']'
    /var/unbound/pfb_dnsbl_lighty.conf:28: error: unknown keyword '=~'
    /var/unbound/pfb_dnsbl_lighty.conf:28: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:28: error: unknown keyword '.*'
    /var/unbound/pfb_dnsbl_lighty.conf:28: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:28: error: unknown keyword '{'
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: unknown keyword '$SERVER['
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: unknown keyword 'socket'
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: unknown keyword ']'
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: unknown keyword '=='
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: unknown keyword '0.0.0.0'
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: stray ':'
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: unknown keyword '8443'
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:29: error: unknown keyword '{'
    /var/unbound/pfb_dnsbl_lighty.conf:30: error: unknown keyword 'ssl.engine'
    /var/unbound/pfb_dnsbl_lighty.conf:30: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:30: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:30: error: unknown keyword 'enable'
    /var/unbound/pfb_dnsbl_lighty.conf:30: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:31: error: unknown keyword 'ssl.pemfile'
    /var/unbound/pfb_dnsbl_lighty.conf:31: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:31: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:31: error: unknown keyword '/var/unbound/dnsbl_cert.pem'
    /var/unbound/pfb_dnsbl_lighty.conf:31: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:32: error: unknown keyword '}'
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: unknown keyword '$SERVER['
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: unknown keyword 'socket'
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: unknown keyword ']'
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: unknown keyword '=='
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: unknown keyword '10.10.10.1'
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: stray ':'
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: unknown keyword '443'
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:34: error: unknown keyword '{'
    /var/unbound/pfb_dnsbl_lighty.conf:35: error: unknown keyword 'ssl.engine'
    /var/unbound/pfb_dnsbl_lighty.conf:35: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:35: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:35: error: unknown keyword 'enable'
    /var/unbound/pfb_dnsbl_lighty.conf:35: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:36: error: unknown keyword 'ssl.pemfile'
    /var/unbound/pfb_dnsbl_lighty.conf:36: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:36: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:36: error: unknown keyword '/var/unbound/dnsbl_cert.pem'
    /var/unbound/pfb_dnsbl_lighty.conf:36: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:37: error: unknown keyword '}'
    /var/unbound/pfb_dnsbl_lighty.conf:39: error: unknown keyword '$HTTP['
    /var/unbound/pfb_dnsbl_lighty.conf:39: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:39: error: unknown keyword 'host'
    /var/unbound/pfb_dnsbl_lighty.conf:39: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:39: error: unknown keyword ']'
    /var/unbound/pfb_dnsbl_lighty.conf:39: error: unknown keyword '=~'
    /var/unbound/pfb_dnsbl_lighty.conf:39: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:39: error: unknown keyword '.*'
    /var/unbound/pfb_dnsbl_lighty.conf:39: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:39: error: unknown keyword '{'
    /var/unbound/pfb_dnsbl_lighty.conf:40: error: unknown keyword 'url.rewrite-once'
    /var/unbound/pfb_dnsbl_lighty.conf:40: error: unknown keyword '='
    /var/unbound/pfb_dnsbl_lighty.conf:40: error: unknown keyword '('
    /var/unbound/pfb_dnsbl_lighty.conf:40: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:40: error: unknown keyword '.*'
    /var/unbound/pfb_dnsbl_lighty.conf:40: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:40: error: unknown keyword '=>'
    /var/unbound/pfb_dnsbl_lighty.conf:40: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:40: error: unknown keyword 'index.php'
    /var/unbound/pfb_dnsbl_lighty.conf:40: error: stray '"'
    /var/unbound/pfb_dnsbl_lighty.conf:40: error: unknown keyword ')'
    /var/unbound/pfb_dnsbl_lighty.conf:41: error: unknown keyword '}'
    /var/unbound/pfb_dnsbl_lighty.conf:42: error: unknown keyword '}'
    read /var/unbound/test/unbound.conf failed: 268 errors in configuration file

                So first off, was it supposed to be .*conf? Or *.conf? Secondly, what's this pfb_dnsbl_lighty.conf file?

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

                  @veldkornet said in pfBlockerNG-devel feedback:

                  So first off, was it supposed to be .*conf? Or *.conf? Secondly, what's this pfb_dnsbl_lighty.conf file?

                  No this is not the correct way. Moving the asterisk as you did will include other temporary files that are in that folder.

                  You seem to have some other issue with the Resolver configuration.

                  Goto the pfSense DNS Resolver and increase the log verbosity to 2, and then review the resolver.log for additional clues.

                  "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
                  • Y
                    yorke
                    last edited by

                    Hi all
                    Everything was working fine no changes have been made but for the last couple days
                    i have been getting the errors listed below
                    DNSBL OUT OF SYNC
                    *** DNSBL update [ 1308990 ] [ 1308991 ] ... OUT OF SYNC ! *** [ 10/10/18 17:52:40 ]
                    followed listed instructions above to try and correct the errors with no luck
                    DNSBL log attach

                    Also getting
                    domain/ referer feed
                    iadsdk.apple.com [ Unknown ] Unknown
                    DNSBL-HTTPS | Unknown Unknown
                    ocsp.digicert.com [ Unknown ] Unknown
                    www.youtube.com [ Unknown ] Unknown
                    DNSBL-HTTPS | Unknown Unknown
                    DNSBL-HTTPS | Unknown Unknown
                    liveupdate.symantec.com [ Unknown ] Unknown

                    Another
                    disable log under floating rules doesn’t not seem to work for me, i created
                    ipv4 list disable logs for that list and global log is also disable but the rules
                    is still being created with log enable.
                    0_1539269924600_DNSBL.txt

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

                      @yorke

                      The sync is off by one, so its not critical in the sense that its still going to block the domains listed. There is a disrepancy of the number of domains listed in the Unbound DB vs the /dnsbl/ folder.

                      I'd suggest a Force Reload and see if that fixes it.

                      "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
                      • XentrkX
                        Xentrk @BBcan177
                        last edited by Xentrk

                        @bbcan177
                        I started seeing the SQLite3 error myself:

                        Warning: SQLite3::exec(): database disk image is malformed in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3931 
Warning: SQLite3::exec(): database disk image is malformed in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3934 
Warning: SQLite3::query(): Unable to prepare statement: 11, database disk image is malformed in /usr/local/www/widgets/widgets/pfblockerng.widget.php on line 297

                        I first noticed it today when logging on to check for updates. The message appeared after the update.

                        2.4.5-DEVELOPMENT (amd64)
Current Base System: 2.4.5.a.20181025.0115
built on Thu Oct 25 01:16:47 EDT 2018
FreeBSD 11.2-RELEASE-p4
pfBlockerNG	2.2.5_17

                        I read thru the posts on how to fix. Just wanted to know know if there is any information you want before I take action.

                        pfSense 2.4.4_2 | Intel i5-3450 @ 3.10GHz  | AES-NI enabled |  pfBlockerNG | Snort
                        Blog Site: https://x3mtek.com || GitHub: https://github.com/Xentrk

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

                          @xentrk said in pfBlockerNG-devel feedback:

                          I started seeing the SQLite3 error myself:
                          Warning: SQLite3::exec(): database disk image is malformed in /usr/local/pkg/pfblockerng/pfblockerng.inc on

                          This is a different issue. I sent you a PM.

                          "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
                          • JeGrJ
                            JeGr LAYER 8 Moderator
                            last edited by

                            @BBcan177

                            Just saw that _18 was online! Great! So installed it with the new wizard, really nice touch!

                            Quick question before having a bigger look into it: The wizard created an alias on LAN per default. In the corresponding DNSBL page flagged with "CARP beta" there's an option to change that to a CARP VIP: Why not use an Alias for the CARP VIP (on LAN) instead? The advantage would be that a) you don't have to configure a full CARP interface setup (and have problems like in another thread, that pfBNG always uses VHID 1 and that's potentially dangerout!) AND as an alias on top of an existing CARP interface - and I would assume almost every CARP setup uses a CARP VIP on LAN - you won't have to think about syncing either, as Alias-style VIPs on CARPs are synced via VirtualIP standards. Also you would use the already configured (and working) LAN VIP as your carrier and failing over with it, too. So I can see no problems with that.

                            If CARP setting stays, than I'd recommend adding VHID field for configuring that, too, as always using 1 (as said above) is potentially dangerous with other clusters in the same network broadcast domain.

                            Greets,
                            Jens

                            Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

                            If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

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

                              @jegr said in pfBlockerNG-devel feedback:

                              Just saw that _18 was online! Great! So installed it with the new wizard, really nice touch!

                              Thanks. Yes it was on the list of to-do items... List just never stops ;)

                              Quick question before having a bigger look into it: The wizard created an alias on LAN per default. In the corresponding DNSBL page flagged with "CARP beta" there's an option to change that to a CARP VIP: Why not use an Alias for the CARP VIP (on LAN) instead? The advantage would be that a) you don't have to configure a full CARP interface setup (and have problems like in another thread, that pfBNG always uses VHID 1 and that's potentially dangerout!) AND as an alias on top of an existing CARP interface - and I would assume almost every CARP setup uses a CARP VIP on LAN - you won't have to think about syncing either, as Alias-style VIPs on CARPs are synced via VirtualIP standards. Also you would use the already configured (and working) LAN VIP as your carrier and failing over with it, too. So I can see no problems with that.
                              If CARP setting stays, than I'd recommend adding VHID field for configuring that, too, as always using 1 (as said above) is potentially dangerous with other clusters in the same network broadcast domain.

                              I am not a user of CARP, so all feedback appreciated about it.... I can definately add a "VHID" option and will checkout the Alias option also...

                              I will see if one of the pfSense Devs will help offline to ensure I am covering all bases...

                              Appreciated!

                              "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
                              • JeGrJ
                                JeGr LAYER 8 Moderator
                                last edited by

                                @bbcan177 said in pfBlockerNG-devel feedback:

                                I am not a user of CARP, so all feedback appreciated about it.... I can definately add a "VHID" option and will checkout the Alias option also...

                                If no one would report other, I'd go with the Alias option if I'd be you ;) Piggy-backing the existing CARP VIP is far easier than creating a separate CARP interface and is also recommended bei the devs itself to reduce network multicast/broadcasting overhead. :)
                                Offering the CARP option, too, would cover those missing corner cases, whereas someone doesn't use a VIP on LAN (or other interfaces) for some reason or another. :)

                                Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

                                If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

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

                                  Please I need help with strange behaviour of pfBlockerNG-devel in my network.
                                  I have logs full of denied connections to UA servers 176.119.4.9:53 UDP and 176.119.4.8:53 UDP.
                                  After some research I found that pfsense box is asking continuously for PTR 8.4.119.176.in-addr.arpa and PTR 9.4.119.176.in-addr.arpa. According to "lsof -n|grep UDP" on pfsense box process who is generating these reguest is "php_pfb"..:

                                  php_pfb 47639 root 15u IPv4 0xfffff8004cb469e0 0t0 UDP wan_IP:36014->isp_dns_IP:domain

                                  I believe this issue is same as mentioned here.. https://www.reddit.com/r/homelab/comments/9u4nqm/windows_dns_server_dnsexe_sending_to_known_bad/

                                  Thanks for any help

                                  pfBlockerNG-devel 2.2.5_19
                                  pfsense2.4.4-RELEASE (amd64)

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

                                    @drbilek

                                    Increase the pfSense Resolver -> Log Verbosity -> 3 (I can't remember if 2 is enough to log outbound DNS requests). Then review the resolver.log to see which Lan device on your network is making those requests.

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

                                    D 1 Reply Last reply Reply Quote 0
                                    • D
                                      drbilek @BBcan177
                                      last edited by

                                      @bbcan177

                                      I´ve already done that.
                                      This Lan device is internal DNS server. From logs it´s trying to resolve PTR 8.4.119.176.in-addr.arpa and PTR 9.4.119.176.in-addr.arpa queries by contacting 176.119.4.9:53 UDP and 176.119.4.8:53 UDP. But these queries are coming from pfsense box.

                                      In pfsense dns logs is visible that pfsense is asking not only my internal LAN DNS but ISP DNS server as well.
                                      And connections from my LAN DNS server are denied by pfBlockerNG
                                      (to servers 176.119.4.9 and 176.119.4.8 ....this range is blacklisted via feed https://rules.emergingthreats.net/fwrules/emerging-Block-IPs.txt)

                                      1 Reply Last reply Reply Quote 0
                                      • TekGamerT
                                        TekGamer
                                        last edited by TekGamer

                                        I was alerted of a crash recently and had to manually restart the two pfBlocker processes:
                                        pfb_dnsbl - pfBlockerNG DNSBL service
                                        pfb_filter - pfBlockerNG firewall filter service

                                        I am running pfBlockerNG-devel net 2.2.5_22

                                        Crash report begins.  Anonymous machine information:

amd64
11.2-RELEASE-p6
FreeBSD 11.2-RELEASE-p6 #3 518496b29ae(RELENG_2_4_4): Wed Dec 12 07:41:44 EST 2018     root@buildbot2.nyi.netgate.com:/build/ce-crossbuild-244/obj/amd64/ZfGpH5cd/build/ce-crossbuild-244/pfSense/tmp/FreeBSD-src/sys/pfSense

Crash report details:

PHP Errors:
[26-Mar-2019 14:29:44 America/Chicago] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 4096 bytes) in /usr/local/www/pfblockerng/pfblockerng_log.php on line 192
[26-Mar-2019 14:29:44 America/Chicago] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 12288 bytes) in /etc/inc/notices.inc on line 105
                                        BBcan177B 1 Reply Last reply Reply Quote 0
                                        • BBcan177B
                                          BBcan177 Moderator @TekGamer
                                          last edited by

                                          @TekGamer You attempted to open a large log file in the Log browser and it ran out of memory. Either need to download the file and view in an offline viewer or view that file from the shell.

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

                                          TekGamerT 1 Reply Last reply Reply Quote 1
                                          • TekGamerT
                                            TekGamer @BBcan177
                                            last edited by

                                            @BBcan177 Ok, in a future release, is it an option for you have the viewer not attempt to load a log file if it is too large, and just display a message to download it to view in an offline viewer? So it doesn't crash?

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