January 28, 2026
LAN of the Same: Internet Edition
When Every Network is 192.168.1.x
NAT hacks, Tailscale magic, and an IPv6 flame war in your living room
TLDR: The post suggests giving every remote gadget a unique overlay address and letting a small box translate, avoiding the 192.168.1.x clashes. Comments explode into an IPv6 vs reality fight, Tailscale quick-fix cheers, vendor plugs, and veteran warnings about brittle NAT mazes—because cameras still need to work.
The post pitches a surprisingly simple fix for the “every house is 192.168.1.x” nightmare: stop aiming at home addresses at all. Instead, give each remote gadget a unique address on a separate network and have a tiny box on-site translate the traffic. Think: a Raspberry Pi acting as your interpreter so your camera doesn’t argue with your neighbor’s camera. Sounds tidy—until the comments arrive with pitchforks and memes.
First through the door: the IPv6 crusaders yelling “just use IPv6!” and dropping Wikipedia links. Immediately roasted by pragmatists who say ISPs, old gear, and carrier-grade NAT (your internet provider’s wall of translation) make that dream… a dream. The Tailscale fan club flexes with “we solved this already,” touting MagicDNS and human-friendly names for family Jellyfin servers. A founder pops in with a “shameless plug” for sshreach.me, prompting eyerolls and a few sign-ups anyway. Meanwhile, grizzled ops folks warn that once you stack translations, “some traffic works one way, and other traffic disappears,” and you’ll be gaslit by “network team says it’s fine.” The comic relief? A DIYer rolls dice to pick random 10.x subnets to dodge collisions. It’s IPv6 idealism vs. NAT-in-the-trenches realism, with home cameras caught in the crossfire.
Key Points
- •Default consumer router subnets often overlap across sites, creating routing ambiguity when using VPNs.
- •Embedded devices (e.g., cameras, NVRs) cannot run VPN clients, complicating remote access.
- •Port forwarding is unreliable due to ISP resets, multi-layer NAT/CGNAT, and RTSP’s dynamic UDP ports.
- •Routing entire subnets through a VPN works for only one site per prefix; re-addressing is impractical at scale.
- •Overlay addressing with WireGuard and 1:1 NAT assigns unique overlay IPs and translates to local addresses, resolving conflicts.