March 29, 2026
Six or nix?
Building a Mostly IPv6 Only Home Network
One home goes all‑in on the new internet—fans cheer, skeptics groan, privacy alarms blare
TLDR: A home hacker proved you can run a house on IPv6 using translation tools to reach old IPv4 sites. The crowd is split: some say it’s too early and too fussy, others fear privacy risks, while jokesters dream of infinite gadgets—and many can’t try it because their ISP still lacks IPv6.
One brave tinkerer just turned their house into an IPv6‑only zone—think “new internet addresses for everything”—and used translator tools (like NAT64/DNS64, which let new‑style devices talk to old‑style IPv4 sites) to keep the lights on. They even leased their own block of addresses and tunneled it home for a fixed setup. Geeky? Yes. Impressive? Also yes.
But the crowd? Pure drama. The loudest chorus says it’s simply too early. One pragmatist insists we’ll be stuck running both old and new systems for “at least the next decade.” Another commenter says they’ve switched IPv6 off everywhere because the benefits feel like a headache, not a upgrade. Privacy nerves flare too: having every gadget reachable on the open internet gives some folks the “heebie jeebies,” even with firewalls, because it feels like your whole home sits on a digital front porch.
Then come the jokes. One user imagines running “~340 undecillion devices”—aka enough IPs for every toaster, toothbrush, and houseplant—to become the smartest smart home on the block. Meanwhile, real‑world roadblocks crash the party: some ISPs still don’t offer IPv6, and tunneling around it sounds like more pain than gain. The verdict? The build shows an IPv6‑only life is possible with clever tooling, but the comments reveal a messy split between the future‑is‑now crowd and the we’ll‑get‑there‑when‑it‑works camp. Grab the popcorn—and your router manual.
Key Points
- •Leased a static /48 IPv6 prefix from Free Range Cloud and routed it over a WireGuard tunnel to avoid dynamic DHCP-PD prefixes from the ISP.
- •Configured OPNsense with policy-based routing to send LAN traffic through the IPv6 tunnel; reverse DNS set via an external DNS service.
- •Implemented IPv6 addressing using SLAAC (assisted mode with M+O+A) and Kea DHCPv6; Unbound handles DNS for static leases.
- •Allocated /56 per Docker host (/64 per Docker network) and used static IPv6 addresses for physical hosts; retained DHCPv4 for legacy devices.
- •Deployed NAT64 using Jool with 64:ff9b::/96 and a DNS64 server, bridging the VM to WAN to obtain public IPv4 and avoid double NAT.