I've mostly stuck with IPv4 in my LAN, but ive been wanting more and more to more to move to IPv6, if only for the learning experience. Since my ISP only uses 6rd and so I can't get a static IP much less a GUA subnet to use, I'm trying to decide strategy for setting up the network, NAT, etc. And I know it's probably not worth the effort, but again at this point it's more a learning exercise.
I have an OpnSense router and use Unbound on it for DNS, Kea for DHCP, and Caddy for reverse proxy, so I am pretty flexible. What strategies have others employed? I use static addresses assigned at the router's Kea DHCP service for IPv4 for all known devices. I have 4 VLANS for guest, mostly trusted devices like my phone and laptop, private stuff like my NAS, Home Assistant server, and Kubernetes cluster, and IoT for stuff that is private but I don't have as much control over like light switches, cameras, and the TV. I use a pihole on the VLAN my personal devices are on to allow for ad, tracking, and malicious site blocking. And I use Pangolin for external access to some private services. And I have a domain dedicated to LAN devices and another for externally hosted VPS servers. Though I dont host much externally now that I finally got access to fiber and no more asymmetric, slow up speeds from Cable service.
I use static IPv4 addresses in Kea DHCP, mostly to assign devices to VLANs and give devices domain names. I'm guessing that will still be necessary. I rarely use the IP addresses in service setup or browsing to services if I can help it, just domain names. What other concerns should I consider?
Any experiences or advice for similar IPv4 to IPv6 LAN conversions would be greatly appreciated, so I can plan ahead.
The only thing I can tell is that it is totally worthless.
Because you can not have an uga ipv6, then obviously you will have an ula served via dhcpv6 with ipv4 local address (double stack).
And in this point you will realize that most computers implementation select which ip address to use following prio: ipv6 uga -> ipv4 -> ipv6 ula
So even if you do all the things right, your clients will not use it because ipv4 is there and you cannot deselect it because I assume you still want connectivity
Funny, right? :)
I've never heard of anything working that way. The preferred algorithm is RFC 8305 "Happy Eyeballs," which uses whichever network responds first. Even if your clients prefer IPv4, having IPv6 available allows you to access some resources that are not available over IPv4.
Most browsers will only use happy eyeballs with a IPv6 UGA, ULAs are just used as a fallback if IPv4 isn't working. You can work around that by using an unreserved UGA as your ULA but that's pretty dodgy.
Unless you want to use Matter which (from my glancing at the docs) requires IPv6?
Matter uses IPv6 but it does not require you to have IPv6 internet. As long as the router isn't blocking IPv6 router advertisements and IPv6 traffic between devices in your LAN you should be okay.
While matter technically requires IPv6 there are non-confirming devices (glares at Hue) that will only do IPv4. It will work with most of the matter controller networks, because in the end it's a conscious decision to disable IPv4 there.