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

    PfBlockerNG (Not devel) DNSBL not blocking all domains in a custom feed

    Scheduled Pinned Locked Moved pfBlockerNG
    5 Posts 3 Posters 652 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.
    • D
      DiamondCreeper75
      last edited by

      DNSBL not blocking all domains in a custom feed, I've tried CRON and reload.
      PFSENSE VERSION: 2.6.0

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

        @diamondcreeper75
        That version is very old. This means probably no one is using is any more.
        What about removing that version, and install the far superior one : pfBlockerNG-devel 3.1.0_1 ?

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        D 1 Reply Last reply Reply Quote 1
        • D
          DiamondCreeper75 @Gertjan
          last edited by

          @gertjan I was using PfBlockerNG-devel, but I wasn't getting this message on any blocked site.22acae60-7c1a-4794-bf81-8b6a63b9e09b-image.png

          N GertjanG 2 Replies Last reply Reply Quote 1
          • N
            netblues @DiamondCreeper75
            last edited by

            @diamondcreeper75 Well, this means that it was working.
            Going back to the non devel version is useless.

            The intercept page fails ssl verification, since ssl was designed to do this.

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

              @diamondcreeper75
              De activated that redirection of an DNSBL. It won't work.
              Select :

              85db2075-333e-43b4-9f35-91e93c3ad3c2-image.png

              If the webserver, the one used by pfBlockerNG, had a certificate that says it marketplace.google;.com, then that page would have been trusted by your browser.
              Or, you have not that certificate. Actually, from all the DNSBL you have listed in the DNSBL feeds, you have none.
              Conclusion : Yes, it's true, even the sites that serve add pages and such, use all https these days.

              This web server page stating that you visited a page blocked by DNSBL works well for plain http sites. These do not exist any more.

              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.