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

    pfBlockerNG-devel 3.1.0 Not Logging Blocked IPs

    Scheduled Pinned Locked Moved pfBlockerNG
    13 Posts 3 Posters 1.7k 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.
    • P
      ProperCactus Rebel Alliance
      last edited by

      @BBcan177

      P 1 Reply Last reply Reply Quote 0
      • P
        ProperCactus Rebel Alliance @ProperCactus
        last edited by

        Crickets....... awesome! I think maybe this project is dead :/

        M 1 Reply Last reply Reply Quote 0
        • M
          MoonKnight @ProperCactus
          last edited by

          @propercactus

          No problem here

          c2a8d403-30a6-44a6-a29c-b3ad93233f1d-image.png

          --- 24.11 ---
          Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
          Kingston DDR4 2666MHz 16GB ECC
          2 x HyperX Fury SSD 120GB (ZFS-mirror)
          2 x Intel i210 (ports)
          4 x Intel i350 (ports)

          P 1 Reply Last reply Reply Quote 0
          • P
            ProperCactus Rebel Alliance @MoonKnight
            last edited by ProperCactus

            @ciscox Any recommendations on how to fix? Are you running in unbound mode or python mode?

            Also what version pfsense and pfBlockerNG are you running?

            fireodoF M 2 Replies Last reply Reply Quote 0
            • fireodoF
              fireodo @ProperCactus
              last edited by

              @propercactus said in pfBlockerNG-devel 3.1.0 Not Logging Blocked IPs:

              @ciscox Any recommendations on how to fix?

              Maybe doing what in pfblocker genal settings is recommended: " Note: To clear all downloaded lists, uncheck these two checkboxes and 'Save'. Re-check both boxes and run a 'Force Update|Reload' "

              Are you running in unbound mode or python mode?
              Yes
              Also what version pfsense and pfBlockerNG are you running?
              3.1.0
              No problem here neither:
              pfb.png

              Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
              SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
              pfsense 2.8.0 CE
              Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

              P 1 Reply Last reply Reply Quote 0
              • M
                MoonKnight @ProperCactus
                last edited by

                @propercactus

                46f5b77b-0ffd-42dd-a9c6-62a961701506-image.png

                Running pfSense 2.5.2 and newest pfBlockerNG-devel 3.1.0

                bbed2450-7233-4951-b09e-638dade7a831-image.png

                --- 24.11 ---
                Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
                Kingston DDR4 2666MHz 16GB ECC
                2 x HyperX Fury SSD 120GB (ZFS-mirror)
                2 x Intel i210 (ports)
                4 x Intel i350 (ports)

                P 1 Reply Last reply Reply Quote 0
                • P
                  ProperCactus Rebel Alliance @fireodo
                  last edited by

                  @fireodo Yea I've done that heaps coz I had an issue where some of the blocklists were firewalled, I had to allow the IPs for the lists so I been doing the force reload of the lists and stuff a lot.

                  I also reinstalled pfBlockerNG. No improvement.

                  1 Reply Last reply Reply Quote 0
                  • P
                    ProperCactus Rebel Alliance @MoonKnight
                    last edited by

                    @ciscox I'm same specs as you, are you auto generating the firewall rules or are you creating aliases and then setting your own firewall rules based on the aliases?

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      MoonKnight @ProperCactus
                      last edited by MoonKnight

                      @propercactus

                      d519791a-5dc7-4e95-80b2-1c2589e32d78-image.png

                      74539934-a32f-4eba-b7ed-fb0fca509451-image.png

                      --- 24.11 ---
                      Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
                      Kingston DDR4 2666MHz 16GB ECC
                      2 x HyperX Fury SSD 120GB (ZFS-mirror)
                      2 x Intel i210 (ports)
                      4 x Intel i350 (ports)

                      P 1 Reply Last reply Reply Quote 0
                      • P
                        ProperCactus Rebel Alliance @MoonKnight
                        last edited by

                        @ciscox Yea that's where we differ, you're using auto-rules where pfBlocker will create the firewall rules for you. I cannot do that as I need to have some outbound only, some in and out etc, so I'm letting it create the aliases and I've created my own firewall rules using those aliases.

                        I think this might be the difference as if it doesn't create the firewall rules automatically, it may also not be creating ip_block.log.

                        I reckon that's the issue.

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