PfBlockerNG v2 on an Alix
-
-
2.0.2 merged, should be fixed.
-
Have a look-see. Cold boot, fresh install pfBNG, no-DNSBL. Good sofar.
-
Thanks Dok…
The Alexa download occurs the first Tuesday of each month (along with the MaxMind dbs), so that is why you saw it download after the re-install of the pkg. The fix that Dok submitted, was that one of the variables wasn't defined in a global array and would download regardless.
Otherwise, I would really suggest moving to a device with some more space :) Glad that its working for you now...
-
The Alexa download occurs the first Tuesday of each month (along with the MaxMind dbs)…
OK that explains the lock-out from pfSense. Memory overload. Why download big files at almost the same time ? Separate them a day or so ? Just know that clean-up of stale/used Memory takes a time like 2 to 24 hrs. Maybe I can use DNSBL again later in 2.03. Thanks.
No wont't upgrade until need to go beyond fiber 20/20 Mbps, and, K.I.S.S., I believe in compact code and observeable CPU & memory behaviour. Those with octacoreand32GB see notin… ;)
-
2.2.5 & 2.03 plus DNSBL again after 24hrs looking good; 59%Memory 57%/var. Thanks :)
-
A blow-out from DNSBL to error.log. /var up sudden to 76%. See for typical errors in file and more than (config) 20000 lines… I don't like that at all.
-
@hda:
A blow-out from DNSBL to error.log. /var up sudden to 76%. See for typical errors in file and more than (config) 20000 lines… I don't like that at all.
Do you have R/W enabled by default?
-
-
pfBNG 2.0.4 on 2.2.6. See extra.log
Hmmm, when on .ro. (read-only) access to the filesystem seems a failure and when on .rw. it looks OK, but then dnsbl.log is reporting writing problems ? Besides in both cases I see double entries about download reports.
So what is in general the supposed state (ro or rw) for using pfBNG ?
