<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on Corvus Blog</title><link>https://nicoleman0.github.io/blog-site/tags/networking/</link><description>Recent content in Networking on Corvus Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 07 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nicoleman0.github.io/blog-site/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Diagnosing and Hardening a Flaky Pi-hole on a Pi Zero 2W</title><link>https://nicoleman0.github.io/blog-site/posts/pihole-reliability/</link><pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate><guid>https://nicoleman0.github.io/blog-site/posts/pihole-reliability/</guid><description>&lt;p>My Pi-hole had developed an annoying habit as of the last couple of weeks. The web UI would go unreachable, FTL would silently die, and DHCP would stop assigning addresses. The only fix I had was unplugging and replugging the device. Not ideal for something that sits in the middle of your network, especially when you live with other people.&lt;/p>
&lt;p>This post covers how I diagnosed the issue and hardened the setup so that transient failures recover automatically rather than taking down the network.&lt;/p></description></item></channel></rss>