IPv4 update frequency
-
pfsense version: 2.4.4-RELEASE-p2
pfBlockerNG version: 2.1.4_16Hi,
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
-
@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.
-
pfsense: 2.4.4-RELEASE-p2 (amd64)
pfBlockerNG-devel: 2.2.5_22Hi,
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
-
@eric45
Sent you a PM with some follow up tests. -
@eric45 said in IPv4 update frequency:
pfsense version: 2.4.4-RELEASE-p2
pfBlockerNG version: 2.1.4_16Hi,
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!
-
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 :
where : newer version means : less issues
-
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! -
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 :
is good enough for me.
