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

    DNSBL Python Mode GUI table missing on pfSense 2.8.1

    Scheduled Pinned Locked Moved pfBlockerNG
    8 Posts 2 Posters 302 Views 2 Watching
    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.
    • A Offline
      Agneten
      last edited by

      log.txt

      Hi,

      I am running the latest development snapshot of pfSense (2.8.1) combined with pfBlockerNG-devel v3.2.10.

      I am trying to configure the "Python Group Policy" to apply different blocking rules per VLAN. However, I am unable to see the policy table (where to add specific subnets/policies). The GUI remains stuck showing only the "Bypass IPs" field and the message: "This is a preliminary DNSBL Group Policy configuration...".

      The issue seems to be purely within the GUI/PHP, because the Unbound logs confirm that the Python module and the pfBlockerNG scripts are loaded successfully.

      My setup:

      • pfSense 2.8.1 Development Snapshot
      • pfBlockerNG-devel 3.2.10
      • DNSBL Mode: Unbound Python Mode

      Steps taken so far:

      1. Enabled "Unbound Python Mode" and "Python Group Policy".
      2. Saved and performed a Force Update/Reload (multiple times).
      3. Reinstalled the pfBlockerNG-devel package.
      4. Cleared browser cache / tried different browsers.
      5. Verified "Python Control" is enabled.

      Despite this, the GUI does not render the policy table.

      Relevant logs (DNS Resolver) showing success:
      [pfBlockerNG]: init_standard script loaded
      [pfBlockerNG]: pfb_unbound.py script loaded
      notice: init module 0: python

      It appears the backend works, but the frontend fails to recognize that Python is active, preventing me from adding specific group policies.

      Attached is a screenshot of the GUI state.

      Thanks for any assistance.

      GertjanG 2 Replies Last reply Reply Quote 0
      • GertjanG Offline
        Gertjan @Agneten
        last edited by

        @Agneten said in DNSBL Python Mode GUI table missing on pfSense 2.8.1:

        pfSense 2.8.1 Development Snapshot

        2.8.1 left develoopement phase two moths ago.
        Netgate Releases pfSense® Community Edition Version 2.8.1

        @Agneten said in DNSBL Python Mode GUI table missing on pfSense 2.8.1:

        Attached is a screenshot of the GUI state.

        I saw something that looked like a log file. Totally unreadable.

        Don't you see this :

        96c67168-2a4a-4701-a545-b4c61e399c6e-image.png

        ?

        If that info doesn't show up like that, I suspect browser issues ?

        No "help me" PM's please. Use the forum, the community will thank you.

        1 Reply Last reply Reply Quote 0
        • A Offline
          Agneten
          last edited by

          Same view on chrome, edge and firefox:
          8c3b0046-ad7f-40c3-a4aa-fbf5a2945b04-image.png

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

            @Agneten said in DNSBL Python Mode GUI table missing on pfSense 2.8.1:

            I am unable to see the policy table (where to add specific subnets/policies).

            So you can see it ?

            This entry box doesn't generate a "pfSense GUI table". It's just a list of IP addresses, known only to pfBlockerng.

            @Agneten said in DNSBL Python Mode GUI table missing on pfSense 2.8.1:

            I am trying to configure the "Python Group Policy" to apply different blocking rules per VLAN.

            No need to "try" ^^
            Add the IP addresses of the devices on your LAN(s). From then on, the DNS requests from these devices will not be filtered by pfBlockerng.

            Have a look here where I (try to) explain that the group policy can do for your, and the consequences you have to be aware.

            No "help me" PM's please. Use the forum, the community will thank you.

            1 Reply Last reply Reply Quote 0
            • A Offline
              Agneten
              last edited by

              Bedankt!

              According to Gemini, instead of 'this is a preliminary...' there should be a '+' where you can add your own vlans and assign different policies to them.
              So it looks like Gemini is hallucinating or I'll have to wait for the next version.

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

                @Agneten

                Who is Gemini ?

                No "help me" PM's please. Use the forum, the community will thank you.

                A 1 Reply Last reply Reply Quote 0
                • A Offline
                  Agneten @Gertjan
                  last edited by

                  @Gertjan Gemini.google.com :-) v3 pro

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

                    @Agneten

                    Pro ? that and they dished the RTFM concept ? 😊

                    @Agneten said in DNSBL Python Mode GUI table missing on pfSense 2.8.1:

                    ....your own (v)lans and assign different policies to them ...

                    pfBlockerng doesn't (afaik) have the functionality to act differently upon LAN networks (aka interfaces) or LAN IPs. That is, it has the more or less 'all or nothing' Python "Group Policy".
                    I hope to be wrong of course.
                    My source : Here it is : 10 lines ...

                    The thing is : unbound is set to listen to all interfaces - port 53, TCP and UDP, for DNS requests.
                    "pfb_unbound.py" is nothing more as a plugin written for unbound. unbound sends the DNSC request to it's plugin, and the plugin can acts (in the main operate function) upon it.
                    Basically, the 10 lines shown above do this : "if the requester IP is member of the policy list, accept the request and return back to unbound to handle it". If not, the comparing with DNSBL lists is done.
                    I agree with the "preliminary" word here. The filtering could be done way more specific. Maybe in the future ?

                    No "help me" PM's please. Use the forum, the community will thank you.

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