<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Home Network on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/home-network/</link>
    <description>Recent content in Home Network on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 29 Jul 2026 09:00:00 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/home-network/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Your Smart Home Devices Deserve a Guest Room</title>
      <link>https://blog.margrop.net/en/post/iot-vlan-guest-room/</link>
      <pubDate>Wed, 29 Jul 2026 09:00:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/iot-vlan-guest-room/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;The short version&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Your bulbs, cameras, robot vacuum, TV, and smart speakers should not permanently share the same local network with your laptops, phones, and NAS. The practical answer is not to disconnect them from the Internet. Give them a separate “guest room”: a separate Wi-Fi name, a separate VLAN, a separate address range, and a firewall that opens only the doors they actually need.&lt;/p&gt;&#xA;&lt;p&gt;This gives you a useful boundary. If an IoT device misbehaves, the problem is less likely to spread to your main network. If an account or firmware is compromised, an attacker does not automatically receive a master key to the whole house.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
    </item>
  </channel>
</rss>
