IPv6 drives me nuts. Not because it's inherently bad, but just because it's unpredictably and inconsistently implemented and supported. I'm on a networking guy

IPv6 drives me nuts. Not because it's inherently bad, but just because it's unpredictably and inconsistently implemented and supported. I'm on a networking guy by any stretch, but I have enough experience to be competent at maintaining home, small business, and server environments. My home provider, modem, router, and device all support IPv6, and when I found out I enabled it. And then, inexplicably, lost the ability to get the Nest app on my phone to connect. The only solve would be to toggle off Wifi and use cell service, let it connect to the Nest service, then turn Wifi back on (it'd work after that point, just couldn't get it to establish the initial connection). The only permanent resolution I could find was to turn IPv6 back off at the router level. The irony is that both my home ISP (Comcast) and my mobile ISP (T-Mobile) are called out in that article as leading in IPv6 deployment. Yet their deployment strategy was varied, and only one led to an issue with connecting to Nest. While the issue was likely something with my internal network/router, if I couldn't figure it out then that gives me a glimpse on how frustrated non-technical users would be. That volatility in and of itself is what drives me nuts with IPv6.