<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linux on family homelab 2026</title><link>https://blog.mychiara.net/tags/linux/</link><description>Recent content in Linux on family homelab 2026</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026</copyright><lastBuildDate>Mon, 06 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.mychiara.net/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>The day my NTP replies left by the wrong door</title><link>https://blog.mychiara.net/posts/004-multihoming-vrf/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.mychiara.net/posts/004-multihoming-vrf/</guid><description>A time server that answers on one interface but replies out another is a classic multi-homing trap — and a zone-based firewall turns it from &amp;lsquo;messy&amp;rsquo; into &amp;lsquo;dropped&amp;rsquo;. Here&amp;rsquo;s the debugging story and the fix: single-home where you can, a management VRF where you can&amp;rsquo;t.</description></item></channel></rss>