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

    pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!

    Scheduled Pinned Locked Moved pfBlockerNG
    94 Posts 27 Posters 88.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.
    • RonpfSR
      RonpfS @Gertjan
      last edited by RonpfS

      @gertjan said in pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!:

      Upgrade .... 3.0.0_x versions are "work in progress".
      3.0.0_8 for me right now :

      The last one was a Copyright update : https://github.com/pfsense/FreeBSD-ports/commits/devel/net/pfSense-pkg-pfBlockerNG-devel

      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
      • ?
        A Former User @Gertjan
        last edited by A Former User

        @gertjan

        If there were no feeds the blocked counter wouldn't be at ~250k ;-)

        here is a screenshot of my full widget

        94860cd5-80b6-4800-980d-4527adabad35-image.png

        1 Reply Last reply Reply Quote 0
        • J
          j.koopmann
          last edited by

          @BBcan177

          Just noticed that with this setup I get DNS SERVFAIL responses if pfBlockerNG matches. Should this not point to the virtual IP so that an error page has chances of being displayed? I am probably missing something.

          F 1 Reply Last reply Reply Quote 1
          • JeGrJ
            JeGr LAYER 8 Moderator @BBcan177
            last edited by

            @bbcan177 said in pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!:

            @j-koopmann

            pfSense 2.4.5 uses Unbound v1.10.1 which has a regression that fails to pass some information to the python modules. It has been fixed, but there is no way to upgrade Unbound to v.1.12.0 in pfSense 2.4.5.

            In pfSense 2.5, it has Unbound v1.13.0.

            For the DNSBL Blocking part, you can enable the checkbox in the DNSBL Tab > DNSBL Event Logging , and that will stop the python integration from logging, and use the DNSBL Webserver to log the events. Unfortunately, that is only limited to HTTP events.

            And for DNS Reply logging, there is no other workaround.

            Not much I can do unfortunately.

            Hey @BBcan177 we already talked about that back when we exchanged mails but: Are you planning on switching trees with the upcoming 2.5 release? Make 3.0.x finally the stable version and go on developing in the devel branch again, so the customers can have a "stable" version again?

            I get asked about that over and over and over and with all the changes in the devel up to 3.x I think it would be time to switch it back to stable so people finally ditch the "oldstable" and get the new one which would make support easier, too :)

            What are your plans on that? And can we perhaps get together again about the whole HA/CARP thing?

            Best wishes!
            Cheers
            \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.

            1 Reply Last reply Reply Quote 0
            • C
              cantor
              last edited by

              Hi,

              I'm on pfSense 2.4.5 and pfBlockerNG 3.0.0.8.

              After enabling the Unbound python mode for DNSBL and doing the Force Reload-DNSBL Unbound Resolver was stopped and did not start again.

              I found the following information in the pfBlocker logfile:
              | ...
              | Starting Unbound Resolver... Not completed. [ 01/22/21 15:41:10 ]
              | error: SSL handshake failed
              | ...

              Saving DNSBL statistics... completed [ 01/22/21 15:41:05 ]
              ------------------------------------------------------------------------
              Assembling DNSBL database...... completed [ 01/22/21 15:41:07 ]
              Added DNSBL Unbound python integration settings
              Adding DNSBL Unbound python mounts:
                Creating: /var/unbound/usr/local/bin
                Mounting: /usr/local/bin
                Creating: /var/unbound/usr/local/lib
                Mounting: /usr/local/lib
              
              Removing DNSBL SafeSearch mode (Resolver adv. setting)
              DNS Resolver ( enabled ) unbound.conf modifications:
                Added DNSBL Unbound Python mode
                Removed DNSBL SafeSearch mode
                Added DNSBL Unbound Python mode script
              
              Saving new DNSBL web server configuration to port [ 8081 and 8443 ]
              Stop Service DNSBL
              VIP address(es) configured
              Restarting DNSBL Service
              Stopping Unbound Resolver
              Unbound stopped in 1 sec.
              Starting Unbound Resolver... Not completed. [ 01/22/21 15:41:10 ]
              error: SSL handshake failed
              
              Restarting DNSBL Service (DNSBL python)
              DNSBL update [ 143616 | PASSED  ]... completed
              ------------------------------------------------------------------------
              
              ===[  GeoIP Process  ]============================================
              
              
              ===[  IPv4 Process  ]=================================================
              
              [ Abuse_Feodo_C2_v4 ]		 Reload . completed ..
                ------------------------------
                Original Master     Final     
                ------------------------------
                1337     1337       1337        [ Pass ]**** 
                -----------------------------------------------------------------
              
              [ Abuse_IPBL_v4 ]		 Reload . completed ..
                Empty file, Adding '127.1.7.7' to avoid download failure.
                ------------------------------
                Original Master     Final     
                ------------------------------
                0        1          1           [ Pass ] 
                -----------------------------------------------------------------
              
              [ Abuse_SSLBL_v4 ]		 Reload . completed ..
                ------------------------------
                Original Master     Final     
                ------------------------------
                123      109        109         [ Pass ] 
                -----------------------------------------------------------------
              
              [ BBC_C2_v4 ]			 Downloading update [ 01/22/21 15:41:11 ] . cURL Error: 28
              Resolving timed out after 15001 milliseconds Retry in 5 seconds...
              . cURL Error: 28
              Resolving timed out after 15000 milliseconds Retry in 5 seconds...
              . cURL Error: 28
              Resolving timed out after 15003 milliseconds Retry in 5 seconds...
              .. unknown http status code | 0
              

              (Re-)starting Unbound Resolver under Services/DNS Resolver/General Settings is also not possible. I get the rerror
              | can't open file pfb_unbound.py for reading

              Jan 22 15:47:55 	unbound 	77509:0 	fatal error: failed to setup modules
              Jan 22 15:47:55 	unbound 	77509:0 	error: module init for module python failed
              Jan 22 15:47:55 	unbound 	77509:0 	error: pythonmod: can't open file pfb_unbound.py for reading
              Jan 22 15:47:55 	unbound 	77509:0 	notice: init module 0: python
              Jan 22 15:47:15 	filterdns 		failed to resolve host pool.ntp.org will retry later again.
              Jan 22 15:47:15 	filterdns 		failed to resolve host time.windows.com will retry later again.
              Jan 22 15:47:15 	filterdns 		failed to resolve host time.nist.gov will retry later again.
              Jan 22 15:45:15 	filterdns 		failed to resolve host pool.ntp.org will retry later again.
              Jan 22 15:45:04 	filterdns 		merge_config: configuration reload
              Jan 22 15:44:15 	filterdns 		failed to resolve host time.windows.com will retry later again.
              Jan 22 15:44:15 	filterdns 		failed to resolve host time-nw.nist.gov will retry later again.
              Jan 22 15:44:15 	filterdns 		failed to resolve host time-b.nist.gov will retry later again.
              Jan 22 15:44:15 	filterdns 		failed to resolve host time.nist.gov will retry later again.
              Jan 22 15:44:15 	filterdns 		failed to resolve host pool.ntp.org will retry later again.
              Jan 22 15:44:15 	filterdns 		failed to resolve host time-a.nist.gov will retry later again.
              Jan 22 15:43:15 	filterdns 		failed to resolve host time-nw.nist.gov will retry later again.
              Jan 22 15:43:15 	filterdns 		failed to resolve host time.windows.com will retry later again.
              Jan 22 15:43:15 	filterdns 		failed to resolve host time-b.nist.gov will retry later again.
              Jan 22 15:43:15 	filterdns 		failed to resolve host time.nist.gov will retry later again.
              Jan 22 15:43:15 	filterdns 		failed to resolve host time-a.nist.gov will retry later again.
              Jan 22 15:43:15 	filterdns 		failed to resolve host pool.ntp.org will retry later again.
              Jan 22 15:42:15 	filterdns 		failed to resolve host time-nw.nist.gov will retry later again.
              Jan 22 15:42:15 	filterdns 		failed to resolve host time.windows.com will retry later again.
              Jan 22 15:42:15 	filterdns 		failed to resolve host time-b.nist.gov will retry later again.
              Jan 22 15:42:14 	filterdns 		failed to resolve host pool.ntp.org will retry later again.
              Jan 22 15:42:14 	filterdns 		failed to resolve host time-a.nist.gov will retry later again.
              Jan 22 15:42:14 	filterdns 		failed to resolve host time.nist.gov will retry later again.
              Jan 22 15:41:10 	unbound 	38108:0 	notice: init module 0: python
              Jan 22 15:41:09 	unbound 	61187:0 	info: 2.000000 4.000000 5
              Jan 22 15:41:09 	unbound 	61187:0 	info: 1.000000 2.000000 2
              Jan 22 15:41:09 	unbound 	61187:0 	info: 0.524288 1.000000 5
              Jan 22 15:41:09 	unbound 	61187:0 	info: 0.131072 0.262144 3
              Jan 22 15:41:09 	unbound 	61187:0 	info: 0.032768 0.065536 2
              Jan 22 15:41:09 	unbound 	61187:0 	info: 0.016384 0.032768 2
              Jan 22 15:41:09 	unbound 	61187:0 	info: 0.008192 0.016384 1
              Jan 22 15:41:09 	unbound 	61187:0 	info: lower(secs) upper(secs) recursions
              Jan 22 15:41:09 	unbound 	61187:0 	info: [25%]=0.065536 median[50%]=0.714573 [75%]=2
              Jan 22 15:41:09 	unbound 	61187:0 	info: histogram of recursion processing times
              Jan 22 15:41:09 	unbound 	61187:0 	info: average recursion processing time 0.996802 sec
              Jan 22 15:41:09 	unbound 	61187:0 	info: server stats for thread 1: requestlist max 36 avg 6.6 exceeded 0 jostled 0
              Jan 22 15:41:09 	unbound 	61187:0 	info: server stats for thread 1: 26 queries, 6 answers from cache, 20 recursions, 0 prefetch, 0 rejected by ip ratelimiting
              Jan 22 15:41:09 	unbound 	61187:0 	info: 1.000000 2.000000 1
              Jan 22 15:41:09 	unbound 	61187:0 	info: 0.524288 1.000000 2
              Jan 22 15:41:09 	unbound 	61187:0 	info: 0.262144 0.524288 2
              Jan 22 15:41:09 	unbound 	61187:0 	info: 0.016384 0.032768 3
              Jan 22 15:41:09 	unbound 	61187:0 	info: 0.008192 0.016384 2
              Jan 22 15:41:09 	unbound 	61187:0 	info: lower(secs) upper(secs) recursions
              Jan 22 15:41:09 	unbound 	61187:0 	info: [25%]=0.0191147 median[50%]=0.032768 [75%]=0.643216
              Jan 22 15:41:09 	unbound 	61187:0 	info: histogram of recursion processing times
              Jan 22 15:41:09 	unbound 	61187:0 	info: average recursion processing time 0.391598 sec
              Jan 22 15:41:09 	unbound 	61187:0 	info: server stats for thread 0: requestlist max 8 avg 3.3 exceeded 0 jostled 0
              Jan 22 15:41:09 	unbound 	61187:0 	info: server stats for thread 0: 12 queries, 2 answers from cache, 10 recursions, 0 prefetch, 0 rejected by ip ratelimiting
              Jan 22 15:41:09 	unbound 	61187:0 	info: service stopped (unbound 1.10.1).
              Jan 22 15:40:15 	unbound 	61187:0 	info: generate keytag query _ta-4f66. NULL IN
              Jan 22 15:40:15 	unbound 	61187:1 	info: generate keytag query _ta-4f66. NULL IN
              Jan 22 15:40:09 	unbound 	61187:0 	info: start of service (unbound 1.10.1).
              Jan 22 15:40:09 	unbound 	61187:0 	notice: init module 1: iterator
              Jan 22 15:40:09 	unbound 	61187:0 	notice: init module 0: validator
              Jan 22 15:40:02 	unbound 	44212:0 	info: 4.000000 8.000000 1
              Jan 22 15:40:02 	unbound 	44212:0 	info: 2.000000 4.000000 3
              Jan 22 15:40:02 	unbound 	44212:0 	info: 1.000000 2.000000 17
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.524288 1.000000 43
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.262144 0.524288 144
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.131072 0.262144 146
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.065536 0.131072 116
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.032768 0.065536 71
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.016384 0.032768 287
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.008192 0.016384 132
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.004096 0.008192 8
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.000000 0.000001 39
              Jan 22 15:40:02 	unbound 	44212:0 	info: lower(secs) upper(secs) recursions
              Jan 22 15:40:02 	unbound 	44212:0 	info: [25%]=0.0205371 median[50%]=0.050075 [75%]=0.222867
              Jan 22 15:40:02 	unbound 	44212:0 	info: histogram of recursion processing times
              Jan 22 15:40:02 	unbound 	44212:0 	info: average recursion processing time 0.167938 sec
              Jan 22 15:40:02 	unbound 	44212:0 	info: server stats for thread 1: requestlist max 26 avg 1.89474 exceeded 0 jostled 0
              Jan 22 15:40:02 	unbound 	44212:0 	info: server stats for thread 1: 2826 queries, 1819 answers from cache, 1007 recursions, 0 prefetch, 0 rejected by ip ratelimiting
              Jan 22 15:40:02 	unbound 	44212:0 	info: 2.000000 4.000000 3
              Jan 22 15:40:02 	unbound 	44212:0 	info: 1.000000 2.000000 13
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.524288 1.000000 29
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.262144 0.524288 49
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.131072 0.262144 68
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.065536 0.131072 59
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.032768 0.065536 48
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.016384 0.032768 167
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.008192 0.016384 52
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.004096 0.008192 1
              Jan 22 15:40:02 	unbound 	44212:0 	info: 0.000000 0.000001 24
              Jan 22 15:40:02 	unbound 	44212:0 	info: lower(secs) upper(secs) recursions
              Jan 22 15:40:02 	unbound 	44212:0 	info: [25%]=0.021412 median[50%]=0.0413013 [75%]=0.196126
              Jan 22 15:40:02 	unbound 	44212:0 	info: histogram of recursion processing times
              Jan 22 15:40:02 	unbound 	44212:0 	info: average recursion processing time 0.167664 sec
              Jan 22 15:40:02 	unbound 	44212:0 	info: server stats for thread 0: requestlist max 29 avg 1.26511 exceeded 0 jostled 0
              Jan 22 15:40:02 	unbound 	44212:0 	info: server stats for thread 0: 1484 queries, 971 answers from cache, 513 recursions, 0 prefetch, 0 rejected by ip ratelimiting
              Jan 22 15:40:02 	unbound 	44212:0 	info: service stopped (unbound 1.10.1). 
              

              Any ideas about this problem?

              Regards Jürgen

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

                @cantor Reboot your box

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

                C 1 Reply Last reply Reply Quote 0
                • C
                  cantor @BBcan177
                  last edited by

                  @bbcan177 said in pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!:

                  @cantor Reboot your box

                  Doesn't work. Unbound is still down after reboot and can only be restarted after I uncheck the option "Eable Python Module".

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

                    @cantor
                    Increase the Resolver Log Level to "2", Save/Apply. Do you see any errors?

                    "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
                    • C
                      cantor
                      last edited by

                      @bbcan177 said in pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!:

                      @cantor
                      Increase the Resolver Log Level to "2", Save/Apply.

                      Do you mean "Raw FilterLogs"? If not, where can I change the log level to level "2"?

                      Regards
                      Jürgen

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

                        @cantor said in pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!:

                        Do you mean "Raw FilterLogs"? If not, where can I change the log level to level "2"?

                        pfSense > DNS Resolver > Adv Settings > Log Level > 2

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

                        C 1 Reply Last reply Reply Quote 0
                        • C
                          cantor @BBcan177
                          last edited by

                          @bbcan177

                          1. pfBlockerNG
                            a) Change Unbound -> Unbound python mode
                            b) Save
                            c) Force Reload All
                            d) Reload hangs when restarting Unbound Resolver

                          2. Switching to DNS Resolver tab after click on the logout button
                            a) Start service
                            b) Service does not start

                          Resolver log:

                          Jan 22 22:08:52 	unbound: [44037:0] fatal error: failed to setup modules
                          Jan 22 22:08:52 	unbound: [44037:0] error: module init for module python failed
                          Jan 22 22:08:52 	unbound: [44037:0] error: pythonmod: can't open file pfb_unbound.py for reading
                          Jan 22 22:08:51 	unbound: [44037:0] notice: init module 0: python
                          Jan 22 22:07:49 	unbound: [82094:0] notice: init module 0: python
                          Jan 22 22:07:49 	unbound: [51734:0] info: 4.000000 8.000000 1
                          Jan 22 22:07:49 	unbound: [51734:0] info: 2.000000 4.000000 2
                          Jan 22 22:07:49 	unbound: [51734:0] info: 1.000000 2.000000 5
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.524288 1.000000 8
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.262144 0.524288 6
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.131072 0.262144 9
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.065536 0.131072 7
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.032768 0.065536 6
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.016384 0.032768 13
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.008192 0.016384 3
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.004096 0.008192 2
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.000000 0.000001 1
                          Jan 22 22:07:49 	unbound: [51734:0] info: lower(secs) upper(secs) recursions
                          Jan 22 22:07:49 	unbound: [51734:0] info: [25%]=0.028672 median[50%]=0.126391 [75%]=0.539154
                          Jan 22 22:07:49 	unbound: [51734:0] info: histogram of recursion processing times
                          Jan 22 22:07:49 	unbound: [51734:0] info: average recursion processing time 0.434923 sec
                          Jan 22 22:07:49 	unbound: [51734:0] info: mesh has 0 recursion states (0 with reply, 0 detached), 0 waiting replies, 63 recursion replies sent, 0 replies dropped, 0 states jostled out
                          Jan 22 22:07:49 	unbound: [51734:0] info: server stats for thread 1: requestlist max 12 avg 1.77778 exceeded 0 jostled 0
                          Jan 22 22:07:49 	unbound: [51734:0] info: server stats for thread 1: 113 queries, 50 answers from cache, 63 recursions, 0 prefetch, 0 rejected by ip ratelimiting
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.524288 1.000000 1
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.262144 0.524288 3
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.065536 0.131072 1
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.016384 0.032768 4
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.008192 0.016384 5
                          Jan 22 22:07:49 	unbound: [51734:0] info: 0.004096 0.008192 1
                          Jan 22 22:07:49 	unbound: [51734:0] info: lower(secs) upper(secs) recursions
                          Jan 22 22:07:49 	unbound: [51734:0] info: [25%]=0.0126976 median[50%]=0.022528 [75%]=0.283989
                          Jan 22 22:07:49 	unbound: [51734:0] info: histogram of recursion processing times
                          Jan 22 22:07:49 	unbound: [51734:0] info: average recursion processing time 0.128478 sec
                          Jan 22 22:07:49 	unbound: [51734:0] info: mesh has 0 recursion states (0 with reply, 0 detached), 0 waiting replies, 15 recursion replies sent, 0 replies dropped, 0 states jostled out
                          Jan 22 22:07:49 	unbound: [51734:0] info: server stats for thread 0: requestlist max 4 avg 0.933333 exceeded 0 jostled 0
                          Jan 22 22:07:49 	unbound: [51734:0] info: server stats for thread 0: 34 queries, 19 answers from cache, 15 recursions, 0 prefetch, 0 rejected by ip ratelimiting
                          Jan 22 22:07:49 	unbound: [51734:0] info: service stopped (unbound 1.10.1).
                          

                          Regards
                          Jürgen

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

                            @cantor said in pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!:

                            Jan 22 22:08:52 unbound: [44037:0] fatal error: failed to setup modules
                            Jan 22 22:08:52 unbound: [44037:0] error: module init for module python failed
                            Jan 22 22:08:52 unbound: [44037:0] error: pythonmod: can't open file pfb_unbound.py for reading

                            Re-install the package as this file is missing

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

                            C 1 Reply Last reply Reply Quote 0
                            • C
                              cantor @BBcan177
                              last edited by cantor

                              @bbcan177

                              I reinstalled pfBlockerNG and triggered Forced Reload-DNSBL. Everything seemed fine and DNS resolver was up with Unbound python mode.

                              Then I rebooted the box for a second check and unfortunately the resolver was down again with error "can't open file pfb_unbound.py for reading".

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

                                @cantor
                                You can't use RamDisks, since the /var/ folder is wiped on reboot. Need to disable that option, and reinstall once more to get the python script back.

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

                                C 1 Reply Last reply Reply Quote 2
                                • C
                                  cantor @BBcan177
                                  last edited by cantor

                                  @bbcan177

                                  Ouch! That's it. Thanks for your help. Now everything works fine. :-)

                                  1 Reply Last reply Reply Quote 0
                                  • lohphatL
                                    lohphat
                                    last edited by lohphat

                                    I'm looking for a little clarification regarding the unbound config changes after switching to python mode.

                                    1. I've notice that unbound is unstarted after any pfBlockerNG-devel v3.x.x package updates. DNS lookups fail so I have to manually restart it.
                                    2. The docs indicate to change the interface to localhost in unbound. I assume it's the "Outgoing Network Interfaces" (now set to "localhost") and not the "Network Interfaces" (currently set to "all") above it.
                                    3. My DNS settings in general setup already has localhost configured (Disable DNS Forwarder is unchecked) as one of the upstream DNS servers. Do I keep this config or remove 127.0.0.1?
                                      127.0.0.1
                                      9.9.9.9
                                      149.112.112.112
                                      2620:fe::fe
                                      2620:fe::9

                                    So...have I made the correct changes? It seems to be working so far but want a 2nd opinion via another set of eyes to make sure I've understood the intended setup.

                                    SG-3100 24.11-RELEASE (arm) | Avahi (2.2_6) | ntopng (5.6.0_1) | openvpn-client-export (1.9.5) | pfBlockerNG-devel (3.2.1_20) | System_Patches (2.2.20_5)

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

                                      been bombarded by this dont know what happens but im blocking ipv6 everywhere.

                                      [02-Mar-2021 15:29:50 Asia/Manila] PHP Fatal error: Uncaught Error: Class 'Net_IPv6' not found in /etc/inc/util.inc:680
                                      Stack trace:
                                      #0 /etc/inc/util.inc(657): is_ipaddrv6('pagead2.googles...')
                                      #1 /usr/local/www/pfblockerng/www/index.php(59): is_ipaddr('pagead2.googles...')
                                      #2 {main}
                                      thrown in /etc/inc/util.inc on line 680

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

                                        @thegenius21
                                        See also here (not posted in the pfB section although probably a pfB related issue).

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

                                          I have tried to install the latest version of PFblockerNg v3.0 however the initialisation is still running after 30 mins. Unloaded older version and tryting to load latest version but still hangs. What is the CLI to install manually please?

                                          GertjanG BBcan177B 2 Replies Last reply Reply Quote 0
                                          • GertjanG
                                            Gertjan @mikeelawson
                                            last edited by

                                            There's no CLI command to install "pfSense"packages.

                                            What happens when you install a 'simple/small' pfSense package like 'Cron' ?

                                            Troubleshooting Upgrades

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