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

IPv4 update frequency

Scheduled Pinned Locked Moved pfBlockerNG
8 Posts 4 Posters 1.1k 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.
  • E
    eric45
    last edited by Mar 30, 2019, 12:47 PM

    pfsense version: 2.4.4-RELEASE-p2
    pfBlockerNG version: 2.1.4_16

    Hi,

    I've noticed that any IPv4 lists that I have with an update frequency set in hours (ie: hourly, 2, 3, 4, 6, 8, 12) always update every 1 hour (assuming the time-stamp has changed) instead of the actual hourly setting. Lists set to update daily or weekly update exactly when they should.

    The 'General settings / CRON Settings' is set for 'Every hour'.

    I'm running pfsense with pfBlockerNG on a dedicated hardware box. I've also tried this in a VirtualBox VM with the same issue.

    Have I missed a setting somewhere?

    Thanks in advance

    Eric

    B F 2 Replies Last reply Mar 30, 2019, 1:48 PM Reply Quote 0
    • B
      BBcan177 Moderator @eric45
      last edited by BBcan177 Mar 30, 2019, 1:49 PM Mar 30, 2019, 1:48 PM

      @eric45
      I would suggest moving to pfBlockerNG-devel... I'm not actively updating the older version unless there are critical issues. Once you install it, you won't want to go back to the older version anyways. :)

      If the problem still exists after that, let me know.

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

      1 Reply Last reply Reply Quote 1
      • E
        eric45
        last edited by eric45 Mar 31, 2019, 2:27 PM Mar 31, 2019, 2:26 PM

        pfsense: 2.4.4-RELEASE-p2 (amd64)
        pfBlockerNG-devel: 2.2.5_22

        Hi,

        I've just built a new VirtualBox VM (FreeBSD-64), installed pfsense & pfBlockerNG-devel.

        I have 3 IPv4 lists - one set to update every hour, the other two set to update every 4 hours.

        As before, all the lists update every 1 hour - this can be seen in the update log.

        Any ideas?

        Thanks,

        Eric

        B 1 Reply Last reply Apr 9, 2019, 2:27 AM Reply Quote 0
        • B
          BBcan177 Moderator @eric45
          last edited by Apr 9, 2019, 2:27 AM

          @eric45
          Sent you a PM with some follow up tests.

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

          1 Reply Last reply Reply Quote 0
          • F
            fmroeira86 @eric45
            last edited by Mar 1, 2025, 10:11 PM

            @eric45 said in IPv4 update frequency:

            pfsense version: 2.4.4-RELEASE-p2
            pfBlockerNG version: 2.1.4_16

            Hi,

            I've noticed that any IPv4 lists that I have with an update frequency set in hours (ie: hourly, 2, 3, 4, 6, 8, 12) always update every 1 hour (assuming the time-stamp has changed) instead of the actual hourly setting. Lists set to update daily or weekly update exactly when they should.

            The 'General settings / CRON Settings' is set for 'Every hour'.

            I'm running pfsense with pfBlockerNG on a dedicated hardware box. I've also tried this in a VirtualBox VM with the same issue.

            Have I missed a setting somewhere?

            Thanks in advance

            Eric

            This is happening with me on 3.2.0_8 version...

            @BBcan177 any idea? thank you!

            G 1 Reply Last reply Mar 6, 2025, 10:00 AM Reply Quote 0
            • G
              Gertjan @fmroeira86
              last edited by Gertjan Mar 6, 2025, 10:01 AM Mar 6, 2025, 10:00 AM

              @fmroeira86

              Imho, 2.4.4 can 't be used outside of a museum.
              You can use it, of cousre, but you're mostly on you own as no one, we humans, remembers issues that are that old. That said, the forum does, so : for you : the search button !?

              pfBlockerng :

              8bd99173-65b6-4c34-9533-62db4a8b50fe-image.png

              where : newer version means : less issues ๐Ÿ˜Š

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

              F 1 Reply Last reply Mar 6, 2025, 10:36 AM Reply Quote 0
              • F
                fmroeira86 @Gertjan
                last edited by Mar 6, 2025, 10:36 AM

                @Gertjan

                I appreciate your willingness to help, but perhaps the issue isn't with my time machine. ๐Ÿ˜‰ I'm actually using version 3.2.0_8, as I mentioned, so no need to worryโ€”Iโ€™m not ready for the museum just yet. If you have any suggestions for this issue on the more recent version, Iโ€™d be grateful!

                G 1 Reply Last reply Mar 6, 2025, 11:09 AM Reply Quote 0
                • G
                  Gertjan @fmroeira86
                  last edited by Mar 6, 2025, 11:09 AM

                  @fmroeira86

                  Do what I do : use de "dev" version : the same as the non dev and probably less issues.
                  True, I don't use pfSense 2.7.2 (can't afford it), so maybe both my pfBlockerng versions are different ?
                  I see 0_16 for the non dev version and the devel version shows 3.2.1_22 for me.

                  Btw : update frequency : I've set mine to "ones a week" as most lists don't update that often.
                  After all, if every pfBlockerng and PI-hole and others update their lists every hours, the lists get hit so hard that the hosting comapny will bill the guy who makes the list, and it would become to expensive for a free service. When that happens, the lists tend to 'die'. Some good ones - some say the best - are already gone for this very reason.

                  So :

                  0ebfe713-d809-4569-8e39-1b5a3c8ab91c-image.png

                  is good enough for me.

                  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.
                    This community forum collects and processes your personal information.
                    consent.not_received