Recent content by bibikalka

This is a fantastic discussion here, and a lot of robust debate! I think the arguments for running PiHole on separate devices actually directly confirm that the resource usage is negligible. And if this is the case - then one might as well run PiHole on the router itself! One can probably tweak...

I was able to replace Diversion with PiHole, so both of these are router entities. Thanks again for pushing this project forward! And, there is no performance impact on the router. So it's literally a free PiHole instance, no extra devices and no new electricity consumption. If I had a Proxmox...

Depending on the Raspberry Pi vintage, I think the Asus router hardware is likely to be faster. Proxmox is of course different!

And, I hear it gets really cold in Canada, so one can use all the waste heat ! :)

Right. I have a Proxmox box sitting switched off where I thought I'd have more use, such as a Home Assistant. But not yet. So don't want to keep it running just for PiHole. Say the extra device wants 10 watts of power. That is 88 kWh per year, which at my rates is slightly above $10. I already...

There is no internet without the router, yes? So a separate PiHole does not solving any additional issues. The biggest question if the router PiHole crashes and does not recover, which would be a major nuisance. It appears robust enough. Therefore the fewer hardware pieces, the better! Unless...

I've been running PiHole on AC86u for a few months now. The router is rebooted nightly. So far I have not seen any DNS outages caused by PiHole - so it appears robust. The web interface for PiHole takes probably 4-5 seconds to spin up from the cold state, then a few more seconds after I type in...

This version appears to be slightly more user friendly. Memory usage dropped. Thank you again for staying on top of this, and updating the versions as they come out!!!

Upgraded - will see how it goes ...

@Martinski After I installed the latest version 3.2.5 I got a couple of reboots that kept the old messages file. So things are back to normal it seems. Full mystery what it was ...

Alright, looks like after setting the history to 15 days, the displayed memory dropped. admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/etc/pihole# ls -lta *.db -rw-r----- 1 pihole pihole 227610624 Nov 25 21:28 pihole-FTL.db -rw-r----- 1 pihole pihole 6344704 Nov 23 09:43 gravity.db -rw-r----- 1...

That's a good point. How do I shrink it?

admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/etc/pihole# ls -lta *.db -rw-r----- 1 pihole pihole 227610624 Nov 24 12:29 pihole-FTL.db -rw-r----- 1 pihole pihole 6344704 Nov 23 09:43 gravity.db -rw-r----- 1 pihole pihole 13426688 Nov 13 10:15 gravity_old.db -rw-r----- 1 pihole pihole 3387392...

Debug log today - without a reboot yet.

It does not take much for memory to skyrocket: admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# /opt/etc/init.d/S65pihole-FTL restart Shutting down pihole-FTL... done. Starting pihole-FTL... done. admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# ps wT | grep...