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 78.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
      SachaH
      last edited by

      First of all, great job on this release!

      I'm currently running 3.0.0_1 with 'Unbound python mode' enabled in DNSBL.
      While viewing the Reports tab I saw that the If and Source columns show 'Unknown' within the DNSBL Python alert entry's.

      Any suggestion how the fix this?

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

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

        Reports tab I saw that the If and Source columns show 'Unknown' within the DNSBL Python alert entry's.

        https://forum.netgate.com/topic/158597/interface-and-source-is-unknown-running-devel-3-0-1/5

        S 1 Reply Last reply Reply Quote 1
        • S
          SachaH @RonpfS
          last edited by

          @RonpfS Thanks 👍 😊

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

            also https://www.reddit.com/r/pfBlockerNG/comments/k1137y/reports_dnsbl_python_unknown/

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

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • RonpfSR
                RonpfS
                last edited by

                and https://www.patreon.com/posts/nov-update-43770381

                1 Reply Last reply Reply Quote 1
                • H
                  HuskerDu
                  last edited by

                  Thanks BBcan177 for your great work,

                  For info, get yellow icon for DNSBL widget due to following error.

                  2020-11-27 21:33:25,736|ERROR| [pfBlockerNG]: Failed get_q_name_qinfo: in method '_get_qname', argument 1 of type 'struct query_info *'
                  
                  BBcan177B 1 Reply Last reply Reply Quote 0
                  • BBcan177B
                    BBcan177 Moderator @HuskerDu
                    last edited by

                    @HuskerDu
                    Do you have any of these options enabled in the DNS Resolver?

                    DHCP Registration:

                    • Static DHCP
                    • OpenVPN Clients

                    If so, disable those options, clear the py_error log and Force Reload - DNSBL and see if the error returns.

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

                    H 1 Reply Last reply Reply Quote 0
                    • H
                      HuskerDu @BBcan177
                      last edited by

                      @BBcan177
                      The options were removed after I've read the doc, but first launch after the install must have triggered the error.

                      Thanks, clearing the log file solved the yellow icon "issue".

                      Regards,

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

                        @BBcan177

                        with v3.0.0 load on my Firewall is significant reduced when running large Set of DNSBL Lists (~3 Million Domains).
                        9e1a09e4-81b1-45fa-9a80-2aa1052914e3-image.png

                        I don't see the unbound-control process spinning up every couple of seconds anymore.

                        Well Done👍

                        1 Reply Last reply Reply Quote 4
                        • F
                          fmroeira86
                          last edited by

                          @BBcan177

                          Thank you for your effort!

                          Everytime I do a RELOAD the skew on the backup CARP gets its value set to 0.

                          This causes the backup machine holding as CARP master when the Master machine comes online again.

                          I'm running 3.0.0_2

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

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

                            Thank you for your effort!
                            Everytime I do a RELOAD the skew on the backup CARP gets its value set to 0.
                            This causes the backup machine holding as CARP master when the Master machine comes online again.
                            I'm running 3.0.0_2

                            Did you update the package on all Nodes?
                            Did you set the SKEW on all nodes correctly?

                            The package should not be syncing the SKEW to the other nodes.

                            See the relevant code here:
                            https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG-devel/files/usr/local/pkg/pfblockerng/pfblockerng.inc#L9349-L9352

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

                            provelsP F 2 Replies Last reply Reply Quote 0
                            • provelsP
                              provels @BBcan177
                              last edited by

                              @bbcan177
                              I got an alert today that an update from 3.0.0_2 => 3.0.0_3 was available. I had already updated to 3.0.0_3.
                              But my package manager now shows 3.0.0_2 as current and wants me to revert.
                              Any problem here? Thanks for reading.
                              b8d2ee71-4444-4f4f-8642-88278ae694ad-image.png

                              Peder

                              MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                              BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

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

                                @provels
                                No Idea. That is outside of the pkg as its part of the pfSense package manager.

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

                                provelsP 1 Reply Last reply Reply Quote 0
                                • A
                                  asmodeus @BBcan177
                                  last edited by

                                  @bbcan177 After upgrading to 3.0.0_3 whitelisting domains from the list of blocked domains (e.g. /pfblockerng/pfblockerng_alerts.php?filterdnsbl=DNSBL_Malicious2) no longer worked - getting 504 Gateway Time-out errors after selecting the domain to whitelist and providing the options (wildcard or not etc.)

                                  The entire UI is unresponsive after that and I can get it back up again via ssh with /etc/rc.php-fpm_restart. I have rolled back to 3.0.0_2 but I still have this issue.

                                  Any ideas on what the issue might be?

                                  BBcan177B 1 Reply Last reply Reply Quote 0
                                  • provelsP
                                    provels @BBcan177
                                    last edited by

                                    @bbcan177
                                    Must have been a personal problem. Rebooted the FW, GUI still offered upgrade to _2 when _3 was already installed. Did pkg upgrade from shell, offered _2 to _3. Went ahead and installed, seems fine now. Go figure.

                                    Peder

                                    MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                                    BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

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

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

                                      @bbcan177 After upgrading to 3.0.0_3 whitelisting domains from the list of blocked domains (e.g. /pfblockerng/pfblockerng_alerts.php?filterdnsbl=DNSBL_Malicious2) no longer worked - getting 504 Gateway Time-out errors after selecting the domain to whitelist and providing the options (wildcard or not etc.)
                                      The entire UI is unresponsive after that and I can get it back up again via ssh with /etc/rc.php-fpm_restart. I have rolled back to 3.0.0_2 but I still have this issue.
                                      Any ideas on what the issue might be?

                                      There are two different things here.

                                      1. Whitelisting
                                      2. Filtering the Alerts tab.

                                      The URL that you posted is for Filtering events, not whitelisting? Write out the steps you took so I can try to reproduce.
                                      It could just be a browser timeout issue if you are trying to view a lot of events? In Alert Settings, what did you set the DNSBL Events number to?

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

                                      A 1 Reply Last reply Reply Quote 0
                                      • F
                                        fmroeira86 @BBcan177
                                        last edited by

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

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

                                        Thank you for your effort!
                                        Everytime I do a RELOAD the skew on the backup CARP gets its value set to 0.
                                        This causes the backup machine holding as CARP master when the Master machine comes online again.
                                        I'm running 3.0.0_2

                                        Did you update the package on all Nodes?
                                        Did you set the SKEW on all nodes correctly?

                                        The package should not be syncing the SKEW to the other nodes.

                                        See the relevant code here:
                                        https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG-devel/files/usr/local/pkg/pfblockerng/pfblockerng.inc#L9349-L9352

                                        Yes.

                                        I'm running the latest version and My main node ovewrites the skew to the secondary one.

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

                                          @fmroeira86

                                          Ok I see the issue.

                                          As reference:
                                          https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG-devel/files/usr/local/pkg/pfblockerng/pfblockerng.inc#L9350-L9351

                                          Can you edit the file: /usr/local/pkg/pfblockerng/pfblockerng.inc, Lines 9350 and 9351

                                          From:

                                          // Remove CARP Advskew setting, if found
                                          if (isset($xml['pfblockerngdnsblsettings']['pfb_dnsvip_skew'])) {
                                              unset($xml['pfblockerngdnsblsettings']['pfb_dnsvip_skew']);
                                          }
                                          

                                          To:

                                          // Remove CARP Advskew setting, if found
                                          if (isset($xml['pfblockerngdnsblsettings' ]['config'][0]['pfb_dnsvip_skew'])) {
                                             unset($xml['pfblockerngdnsblsettings']['config'][0]['pfb_dnsvip_skew']);
                                          }
                                          

                                          I missed adding ['config'][0] to each of those two lines... Sorry about that...

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

                                          F 1 Reply Last reply Reply Quote 0
                                          • A
                                            asmodeus @BBcan177
                                            last edited by asmodeus

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

                                            The URL that you posted is for Filtering events, not whitelisting? Write out the steps you took so I can try to reproduce.

                                            Sure:

                                            1. Coming from the pfBlockerNG dashboard on my Status/Dashboard page, I use the alerts link to review blocked domains in a list. The link points to /pfblockerng/pfblockerng_alerts.php?filterdnsbl=DNSBL_Malicious2
                                            2. Using this list (which takes a while to load) I want to whitelist a domain, so I click on the 'plus' sign to start the process.
                                            3. I specify wildcard no, add description no.
                                            4. Page loads for a while and ultimately I am getting the nginx timeout. (Even when this worked it takes 110 seconds or more to complete)
                                            5. The page I attempted to whitelist is NOT whitelisted.
                                            6. The entire pfsense UI is unresponsive at this point and I resolve by restarting php-fpm via ssh

                                            The Log Settings are set to default (20000 lines), and the Alert Settings are set to default:1000 Stat Table entries and 100 Filter Limit. Are these the Alert Settings you were asking about?

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