<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Homelab on all things oneinsane</title><link>https://www.oneinsane.org/categories/homelab/</link><description>Recent content in Homelab on all things oneinsane</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>webmaster@oneinsane.org (Ron Rosson)</managingEditor><webMaster>webmaster@oneinsane.org (Ron Rosson)</webMaster><copyright>&amp;copy; Copyright 2026 Ronald L. Rosson Jr.</copyright><lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oneinsane.org/categories/homelab/index.xml" rel="self" type="application/rss+xml"/><item><title>Teaching My Home Lab to Watch Itself</title><link>https://www.oneinsane.org/posts/2026-09-03-teaching-my-home-lab-to-watch-itself/</link><pubDate>Thu, 03 Sep 2026 00:00:00 +0000</pubDate><author>webmaster@oneinsane.org (Ron Rosson)</author><guid>https://www.oneinsane.org/posts/2026-09-03-teaching-my-home-lab-to-watch-itself/</guid><description>&lt;p&gt;I&amp;rsquo;ve spent a long time building out a home lab that, frankly, generates more security-relevant noise than I have time to personally review — firewall logs, intrusion detection alerts, DNS oddities, the usual pile that anyone running a real network at home eventually accumulates. For a while my answer was &amp;ldquo;check it when I remember to,&amp;rdquo; which is not a strategy, it&amp;rsquo;s a hope.&lt;/p&gt;</description></item></channel></rss>