Since you are a noobie, I would suggest waiting until the add-on had been approved by IPFire Developers.
If you want to experiment, then there are instructions above in Post #52. But I would not recommend this today unless you are very comfortable with Linux and with IPFire.
Further I think it isn’t a good idea to use RAM for storage of permanent files ( the contents may change ). Logs are also not stored in tmpfs anymore.
The effect can be seen at the graphs after a power loss. The data are stored in /var/log/rrd, which is located in tmpfs. To minimise the loss, periodically the ram disk is stored to HDD.
I discovered an unwanted side effect of using tmpfs for storing /etc/unbound/zonefiles
rpz.tmpxxx files can’t be stored there but unbound does use those rpz lists (like huawei native!) so I had to stop using tmpfs for that!
log excerpt while /etc/unbound/zonefiles was stored in RAM:
Aug 4 21:38:52 black-x86-64 unbound: [630:0] info: generate keytag query _ta-4a5c-4f66. NULL IN
Aug 4 21:38:52 black-x86-64 unbound: [630:0] error: could not open /etc/unbound/zonefiles/HagheziXiaomiNative.rpz.tmp630: Permission denied
Aug 4 21:38:52 black-x86-64 unbound: [630:0] error: could not open /etc/unbound/zonefiles/HagheziDOH.rpz.tmp630: Permission denied
Aug 4 21:38:52 black-x86-64 unbound: [630:0] error: could not open /etc/unbound/zonefiles/HagheziHuaweiNative.rpz.tmp630: Permission denied
Aug 4 21:38:52 black-x86-64 unbound: [630:0] error: could not open /etc/unbound/zonefiles/HagheziLgTVWebOS.rpz.tmp630: Permission denied
Aug 4 21:38:53 black-x86-64 unbound: [630:0] error: could not open /etc/unbound/zonefiles/HagheziPopupAds.rpz.tmp630: Permission denied
Aug 4 21:38:55 black-x86-64 unbound: [630:0] error: could not open /etc/unbound/zonefiles/HagheziMulti.rpz.tmp630: Permission denied
NSFW by OISD - this list blocks P—rn / Adult / Shock / Gore
I have been following Stephan’s subReddit for couple of years, before he switched to www.oisd.nl
License GNU General Public License v3.0
Allowed Update frequency - 1 hour
keep in mind DNS will be noticeable slower with such big files.
Large RPZ files will slow down the unbound reload time and slow down a DNS lookup. Over 500,000 lines of RPZ files (total lines for all RPZ files) is discouraged. Over 1,000,000 lines of RPZ files (total lines for all RPZ files) is NOT recommended.
Hi Jon,
I also have a custom script that collects some tens of thousands IP addresses in the blocklist.conf.
Sources for those are variate: from AD-block sources to IP Block lists.
Question: does RPZ accept sources that are not designed for RPZ?
Why I ask: the block list part attached to unbound does not have the metrics like RPZ so tracking down a false positive is quite hard and involves tcpdump monitoring for NXDOMAIN answers and then whitelisting that domain.
With RPZ I hope this part to be much easier with the help of metrics plus the good loging (a grep -i RPZ does provide good insights in real time)
No.
I once found a “hosts to RPZ” type conversion script while Giggle searching, and I tried writing something similar, but once someone recommended the hagezi lists I set that effort aside. hagezi seems to have everything I needed!