> IPv6 is a disaster. It's too difficult to understand or configure properly That's not really true. If you put a minimum of effort, you should be able to setu

> IPv6 is a disaster. It's too difficult to understand or configure properly That's not really true. If you put a minimum of effort, you should be able to setup a local-only IPv6-subnet quite easily. And going from there to internet routable IPv6 takes almost no effort at all. Yes. There are things which are different from IPv4. But it's not rocket-surgery. If you had any genuine interest in understanding it and put in some effort, you would find most of the "difficulties" are not really all that difficult. If we were to start with a "from scratch" mindset, I would argue it's rather IPv4 which is hard to understand: - subnetting? how? why? - NAT? - port-forwards? - upnp assisted firewall traversal? - upnp UN-assisted firewall traversal? - Forcing app-developers to use UDP over TCP because... lack of end-to-end connectivity and ... again firewall traversal often only being possible with UDP. - And what about carrier grade NATs? And all other kinds of stuff we've just gotten used to being that way. IPv6 solves most of those things right away... So the only thing you have to learn is the addressing-scheme... And that's about it. I think everyone who complains about how IPv6 is "hard" has honestly just forgotten just how terrible hacky (and thus complex!) our IPv4 everyday situation really is.