> And lastly... a lot of IT guys still don't care for IPv6
The issue I have with IPv6 is that it's so complex compared to the IPv4 I know, and still has lacking support in routers and similar.
For example, I want to be sure my local devices uses my local NTP server. With IPv4 it's trivial, I just add an option to the DHCP server. With IPv6 I can't do that with RA, I have to use DHCPv6. But Android doesn't support DHCPv6, so I have to run both RA and DHCPv6, and hope it just works out.
Next there's firewall rules. I used to run pfSense, and it just didn't support changing prefixes. Everything was configured based on the full IPv6 address, so everything had to be reconfigured when the prefix changed. Not only that, but stuff like DNS server address didn't get updated properly, so all the clients still tried to connect to the DNS server (my router) using the old prefix, so no internet for any of the clients all of a sudden.
Additionally, using the full IPv6 address internally is a PITA, since even if I assign a server a nice ::2 ending, my prefix is a full 64 bits of random noise (which changes, yay!). So I ended up using ULAs, which at least preserved some of my sanity, but it's another thing to manage.
So yeah, once I start having IPv6 issues and have to figure out some solution I wonder why bother. Mostly because it's so different, and it's still under development, both specification wise and the implementations. IPv4 for most people is quite simple in comparison, due to an established ecosystem. IPv6 on the other hand feels quite rough, including the impedance mismatches due to clearly being designed for large enterprise networks.
That being said, I've now had IPv6 enabled at home for over a year, things mostly work well. The key change was to ditch pfSense and switch to OpenWRT.
> For example, I want to be sure my local devices uses my local NTP server. With IPv4 it's trivial, I just add an option to the DHCP server. With IPv6 I can't do that with RA, I have to use DHCPv6. But Android doesn't support DHCPv6, so I have to run both RA and DHCPv6, and hope it just works out.
Out of curiosity, why does this require DHCPv6? Cant you just point your local devices to ntp.homedomain (or whatever the DNS name of the local NTP server is)?
I think if you're using the Meinberg NTP client on Windows, or chrony on Linux, that's feasible. Older systems may prefer to snag it from DHCP: which probably would only do IPv4 anyway.
Why are you using IP addresses directly? That's what DNS is for. There's even mDNS for in simple home networks.
(The DHCP thing is valid but that's one single android dev being an ass who can't read deciding that it imposes limitations it doesn't and ruining it for the rest of us)
The issue I have with IPv6 is that it's so complex compared to the IPv4 I know, and still has lacking support in routers and similar.
For example, I want to be sure my local devices uses my local NTP server. With IPv4 it's trivial, I just add an option to the DHCP server. With IPv6 I can't do that with RA, I have to use DHCPv6. But Android doesn't support DHCPv6, so I have to run both RA and DHCPv6, and hope it just works out.
Next there's firewall rules. I used to run pfSense, and it just didn't support changing prefixes. Everything was configured based on the full IPv6 address, so everything had to be reconfigured when the prefix changed. Not only that, but stuff like DNS server address didn't get updated properly, so all the clients still tried to connect to the DNS server (my router) using the old prefix, so no internet for any of the clients all of a sudden.
Additionally, using the full IPv6 address internally is a PITA, since even if I assign a server a nice ::2 ending, my prefix is a full 64 bits of random noise (which changes, yay!). So I ended up using ULAs, which at least preserved some of my sanity, but it's another thing to manage.
So yeah, once I start having IPv6 issues and have to figure out some solution I wonder why bother. Mostly because it's so different, and it's still under development, both specification wise and the implementations. IPv4 for most people is quite simple in comparison, due to an established ecosystem. IPv6 on the other hand feels quite rough, including the impedance mismatches due to clearly being designed for large enterprise networks.
That being said, I've now had IPv6 enabled at home for over a year, things mostly work well. The key change was to ditch pfSense and switch to OpenWRT.