Hi Folks,
I'm most impressed with the above. PiHole has saved me. I'm going to stick with it. However, I'm wondering best way to port it to another rpi. It's been one of those weeks where if it can go wrong, it will. Consequently I installed pihole onto a development rpi. I've cobbled together a script which performs....is this enough to be restore pihole to the rpi on which it needs to be running long term?
Current pihole box is rpi4 with 4Gb ram. Target will be rpi3b with 1Gb ram. Will the rpi3b cope?
The rpi4 is bookworm. I've just installed trixie on the rpi3b. I haven't installed pihole on the rpi3b yet. The rpi4 is called "dns.swampdog". The rpi3b is currently called "dns1.swampdog". It is critical the rpi3b ends up being "dns.swampdog".
Grateful for advice.
TIA
I'm most impressed with the above. PiHole has saved me. I'm going to stick with it. However, I'm wondering best way to port it to another rpi. It's been one of those weeks where if it can go wrong, it will. Consequently I installed pihole onto a development rpi. I've cobbled together a script which performs..
Code:
pihole-FTL --teleportersqlite3 /etc/pihole/pihole-FTL.db ".backup /some/output/path"Current pihole box is rpi4 with 4Gb ram. Target will be rpi3b with 1Gb ram. Will the rpi3b cope?
The rpi4 is bookworm. I've just installed trixie on the rpi3b. I haven't installed pihole on the rpi3b yet. The rpi4 is called "dns.swampdog". The rpi3b is currently called "dns1.swampdog". It is critical the rpi3b ends up being "dns.swampdog".
Grateful for advice.
TIA
Statistics: Posted by swampdog — Mon May 25, 2026 1:25 am
