Blockers to IPv6 Adoption
11–20 of 154 posts
Re: Blockers to IPv6 Adoption
#12For me, there is just one thing that prevents me from switching completely to IPv6: Github.
Re: Blockers to IPv6 Adoption
#13Performance? How exactly is ipv6 more performing? It even has bigger headers. Why would ipv6 be more reliable than ipv4? I’d say it’s the opposite: many times I’ve found websites with AAAA registers that pointed to a dead server. I mean, if you’re going to blame cgn for your problems, let’s steep to your level. Analytics? Forensics? So you’re telling me ipv6 destroys my privacy. How is that a pro argument?
Re: Blockers to IPv6 Adoption
#14I see NO reason to deploy ipv6 at the moment. I don't see it for home lans, I don't see it for my workplace, I don't see it for bigger enterprises.
But you can have a gazillion IPs with ipv6!! Yeah, so what?
Re: Blockers to IPv6 Adoption
#15Re: Blockers to IPv6 Adoption
#16Re: Blockers to IPv6 Adoption
#17Re: Blockers to IPv6 Adoption
#18Re: Blockers to IPv6 Adoption
#19I've enabled ipv6 on my ubuntu server recently and it was 100x slower. The only solution I found is to go back to ipv4: https://askubuntu.com/questions/759524/problem-with-ipv6-sud...
If the former I'd image this is a kernel bug and has nothing to do with any Ubuntu servers.
Re: Blockers to IPv6 Adoption
#20I was hanging out in the IPv6 mailing lists at the time the various solutions were being debated.
The prevailing attitude was "the Internet is about to die from routing overload without IPv6, so we can stick whatever complexity we want inside it, and they will have no choice but to accept it."
Except that new router hardware and new incremental software improvements came out, and the enormous complexity of the "boil the ocean" redesign inherent in IPv6 was rightly regarded as completely unnecessary.
If the IETF had simply made IPV6 "ipv4 with longer addresses", (and there was a proposal to do just that), implementations and deployment would have been dramatically simpler and would have stood a real chance of succeeding.
Instead we have this baroque construction, which I _still_ have to explicitly disable in my work environment because various bits of supposedly IPV6 software don't play nice together.