<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tp-Link on Suraj's Homelab</title><link>https://homelab.surajdhakre.xyz/tags/tp-link/</link><description>Recent content in Tp-Link on Suraj's Homelab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://homelab.surajdhakre.xyz/tags/tp-link/index.xml" rel="self" type="application/rss+xml"/><item><title>Homelab Network Architecture — VLANs, OpenWrt, and a Managed Switch</title><link>https://homelab.surajdhakre.xyz/blog/homelab-network-architecture-vlans-openwrt/</link><pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate><guid>https://homelab.surajdhakre.xyz/blog/homelab-network-architecture-vlans-openwrt/</guid><description>&lt;h2 id="the-problem"&gt;The problem&lt;/h2&gt;
&lt;p&gt;When the homelab was just a Raspberry Pi, everything sat on the same flat network — my gaming PC, phones, TV, and all the homelab services. That&amp;rsquo;s fine until you start running things like Frigate NVR, Pi-hole DNS, and a dozen Docker containers. One misconfigured service and suddenly your gaming session is lagging because Jellyfin is saturating the network with a transcode.&lt;/p&gt;
&lt;p&gt;The fix: &lt;strong&gt;VLANs&lt;/strong&gt;. Separate the homelab into its own isolated network segment, with controlled routing between them.&lt;/p&gt;</description></item></channel></rss>