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

    pfblocker 3.1.0_3

    Scheduled Pinned Locked Moved pfBlockerNG
    14 Posts 5 Posters 1.4k 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.
    • Bob.DigB
      Bob.Dig LAYER 8 @mcury
      last edited by

      @mcury true, I had it enabled and now I can't disable it.

      1 Reply Last reply Reply Quote 1
      • J
        jdeloach @mcury
        last edited by

        @mcury

        Disables and enables just fine on my system.

        Just for the record, I'm running pfSense CE 2.6.0 in case that makes a difference.

        M 1 Reply Last reply Reply Quote 0
        • M
          mcury Rebel Alliance @jdeloach
          last edited by

          @jdeloach said in pfblocker 3.1.0_3:

          Disables and enables just fine on my system.
          Just for the record, I'm running pfSense CE 2.6.0 in case that makes a difference.

          Hm, strange that its working for you and not for us, but thanks for the info
          I'm running 22.01 and pfblocker 3.1.0_3

          dead on arrival, nowhere to be found.

          GertjanG fireodoF 2 Replies Last reply Reply Quote 0
          • GertjanG
            Gertjan @mcury
            last edited by

            It gets even better.

            It stayed 'checked' after I upgraded from .2 to .3 - I didn't test this behavior while I was using .2

            Now at home, I could check it, Save, and it was checked when I re entered the DNSBL page.
            I unchecked, Save, move on to somthing else, came back and it was unchecked.

            So, @home, using .2, it seems to work just fine.

            Btw : because I still don't trusted "GUI's" (that happens when you grow up with Windows since version 1) I also checked the real setting :

            <pfsense>
              <installedpackages>
                <pfblockerngdnsblsettings>
                  <pfb_dnsbl_rule></pfb_dnsbl_rule>
            

            it is un checked.
            If its checked, it would be

                 <pfb_dnsbl_rule>on</pfb_dnsbl_rule>
            

            The thing is, I can't install .3 .....
            as now its version 3.1.0_4

            That what I have now, and it seems to work.

            Btw :

            Maybe its useful to de select all these before un checking the check box :

            f3f17b2d-0dc5-4ac5-b32a-a65b3bc3f0c6-image.png

            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
            • fireodoF
              fireodo @mcury
              last edited by

              @mcury said in pfblocker 3.1.0_3:

              Hm, strange that its working for you and not for us, but thanks for the info
              I'm running 22.01 and pfblocker 3.1.0_3

              I just saw in my settings that on the DSNBL-Settings page the section "DNSBL Configuration" is twice ...

              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.

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

                @fireodo said in pfblocker 3.1.0_3:

                twice

                Isn't that a not a reason for an image ?

                Like :

                4f5ebddf-e7dd-4a5c-8716-d10cc1e50126-image.png

                Can't see

                480d9a35-f78b-42c0-ae4d-1c8dfbe9545c-image.png

                twice.
                Even without glasses.

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

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

                  @gertjan said in pfblocker 3.1.0_3:

                  Isn't that a not a reason for an image ?

                  See here

                  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.

                  1 Reply Last reply Reply Quote 0
                  • fireodoF
                    fireodo @Gertjan
                    last edited by

                    @gertjan said in pfblocker 3.1.0_3:

                    Can't see

                    I dont know why its not the case on your machine ...

                    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.

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

                      @fireodo

                      Your are running 3.1.0_4 (4 for four) right ?

                      3 was really had a short live.

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

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

                        @gertjan said in pfblocker 3.1.0_3:

                        Your are running 3.1.0_4 (4 for four) right ?

                        Now - yes! But the doublette was in 3.1.0_3 😆

                        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.

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

                          All cases closed then 👍

                          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
                          • fireodoF
                            fireodo @Gertjan
                            last edited by

                            @gertjan said in pfblocker 3.1.0_3:

                            3 was really had a short live.

                            Yes, BBcan177 reacted very fast ... 😆 🤣 😆

                            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.

                            M 1 Reply Last reply Reply Quote 0
                            • M
                              mcury Rebel Alliance @fireodo
                              last edited by

                              Yes, after upgrading to 3.1.0_4, everything is fine..
                              Thanks BBcan177 and pfsense team

                              dead on arrival, nowhere to be found.

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