IPv6 is a trap for home labbers

I may be wrong, but hear me out. I've been running a small homelab in Tokyo for three years — Proxmox, few VMs, reverse proxy, standard stuff. Every guide says "enable IPv6, it's the future." But the complexity-to-benefit ratio feels off.

My ISP doesn't even offer static v6 prefix delegation. I get a /64 that changes on reboot. So I need dynamic DNS for v6 too, firewall rules in two stacks, ND proxying for Docker because macvlan + v6 is broken half the time. For what? I can already reach everything I need via v4 + NAT.

The "end-to-end connectivity" argument is nice in theory. In practice, my firewall blocks everything anyway. The "no NAT" benefit? I still want NAT for network segmentation.

Am I missing something, or is this just complexity theater for home users?

IPv6 on the vps side, v4 only at home. It actually works and I dont think about dual stack at all.

[Interface]
Address = 10.200.200.2/32
DNS = 1.1.1.1

[Peer]
PublicKey =...
AllowedIPs = 0.0.0.0/0,::/0
Endpoint = hetzner.com:51820

Not saying youre wrong about complexity. Just saying theres a cheat code

Kenji3, as far as I know, your experience is typical for residential connections in many markets, to be precise. The regulatory angle matters here. Under GDPR, IP addresses are personal data. IPv4 + NAT provides a form of natural obfuscation — your household shares one address. IPv6's /64 or /56 assignment can identify individual devices across sessions, and many home routers leak the full 128-bit address in outbound connections. I have documented this with packet captures. The "trap" framing is too strong. Prefix delegation works well with proper CPE. The issue is ISP implementation quality, not protocol design. Your ISP's failure to provide stable delegation is a market failure, not a technical one. I run dual-stack at home with a static /48 from RackNerd (https://www.racknerd.com). Stable for two years. The complexity is front-loaded; after initial setup, maintenance is minimal.