I agree that the Zero is up to the task, but I prefer a wired connection for my home DNS/DHCP server and if I understand correctly the Pi5 has better wired ethernet than its predecessors… Yeah, utilization is laughable, but there’s something to be said for reduced lag time too:
Hostname: pihole
CPU:0.2% on4 cores running 318 processes (0.3% used by FTL)
RAM:25.9% of2.0 GB is used (7.4% used by FTL)
Swap:35.9% of512.0 MB is used
Kernel: Linux pihole 6.12.25+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64
Uptime: a month (running since Sunday, May 18th 2025, 17:54:59
I have never felt the need to have a wired connection for my DNS/DHCP, since such a trivial amount of data exchanges hands. The quality of the wired connection if it had one would similarly have negligible impact, surely.
For me it’s not about the bandwidth, it’s about the lag and reliability. I have had strong WiFi connections flake out a lot more than wired connections.
Also, I just prefer to not have 100+ WiFi devices kicking around my network when more than half of them could be wired, or on another protocol like Zigbee.
I guess I am pretty far from saturating my WiFi in any way, the removal of cables with little to no impact on connectivity was far more of a priority for me. I have never noticed a WiFi related outage or performance loss.
My WiFi routers have historically struggled a bit, I’ve got a decent one now, but even it is slow to manage the DHCP lists for fixed assignments by MAC address.
Yeah… I’m not going to stick a clunky old laptop on top of my bookshelf and have it run 24/7 as my PiHole. My Pi Zero 2 W is far more appropriate.
No reason why a laptop wouldn’t work though.
I mean, a lot of things would work, I could power it all with potato batteries if I had enough. The Pi Zero 2 W only cost ~£15 anyway.
I agree that the Zero is up to the task, but I prefer a wired connection for my home DNS/DHCP server and if I understand correctly the Pi5 has better wired ethernet than its predecessors… Yeah, utilization is laughable, but there’s something to be said for reduced lag time too:
Hostname: pihole CPU: 0.2% on 4 cores running 318 processes (0.3% used by FTL) RAM: 25.9% of 2.0 GB is used (7.4% used by FTL) Swap: 35.9% of 512.0 MB is used Kernel: Linux pihole 6.12.25+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 Uptime: a month (running since Sunday, May 18th 2025, 17:54:59I have never felt the need to have a wired connection for my DNS/DHCP, since such a trivial amount of data exchanges hands. The quality of the wired connection if it had one would similarly have negligible impact, surely.
For me it’s not about the bandwidth, it’s about the lag and reliability. I have had strong WiFi connections flake out a lot more than wired connections.
Also, I just prefer to not have 100+ WiFi devices kicking around my network when more than half of them could be wired, or on another protocol like Zigbee.
I guess I am pretty far from saturating my WiFi in any way, the removal of cables with little to no impact on connectivity was far more of a priority for me. I have never noticed a WiFi related outage or performance loss.
My WiFi routers have historically struggled a bit, I’ve got a decent one now, but even it is slow to manage the DHCP lists for fixed assignments by MAC address.
But… that’s so uncool…
I should have rebuilt an old coffee maker in to a Pi Hole instead. I’m such a rube.