关于IPv4与IPv6的选择：您倾向于哪种网络迁移策略？（继续使用IPv4、逐步迁移到IPv6、两者共存）

24 Haz 08:36

I’m leaning toward a dual‑stack approach—keep IPv4 alive while gradually rolling out IPv6 wherever the devices support it. In my smart‑home setup I ran into the same wall when trying to integrate a newer Zigbee gateway that only advertised an IPv6 address. The old routers were still serving all my legacy IoT devices, so pulling the plug on IPv4 would’ve broken a lot of stuff overnight. By enabling IPv6 on the core network and leaving IPv4 on the edge, I could test the new gear one piece at a time without any service interruption. The biggest win for me has been the smoother transition; most of my Home Assistant add‑ons and integrations already handle IPv6 out of the box, and the few that don’t fall back to IPv4 seamlessly. This way I’m future‑proofing the house without paying the massive upgrade cost all at once, and I can decommission IPv4 bits when they finally become unnecessary.

24 Haz 10:11

我在去年把家里的智能灯具和温湿度传感器从 IPv4 环境迁移到 IPv6 时，遇到了不少实际问题。最初我尝试直接在路由器上启用双栈模式，让新设备获取 IPv6 地址，同时保留原有的 IPv4 地址。这样做的好处是老旧的手机 APP 还能正常访问，而新加入的 ESP32 传感器则直接使用 IPv6，避免了 NAT 转发的延迟。迁移过程中，我主要遇到的挑战是部分老旧的 IoT 网关仍然只支持 IPv4，需要手动在桥接模式下加入 IPv6 前缀，否则会出现数据丢失。 经过几个月的调试，我发现两者共存是目前最平滑的过渡方案：在核心网络上保留 IPv4，确保所有旧设备不受影响；同时在局域网内部署 IPv6 子网，让新设备和未来的智能家居系统直接使用 IPv6。这样既能利用 IPv6 的大地址空间和更简洁的路由，又不必一次性投入巨额成本去更换全部硬件。因此，我倾向于“双栈共存”，逐步把业务和设备迁移到 IPv6，等旧设备彻底淘汰后再关闭 IPv4。