IPv6 has been around for two decades and accounts for less than 1 percent of Internet traffic, making it's adoption one of the biggest failures in IT.
Turns out that backwards compatibility is kind of a big deal. Any of you guys made the jump? Any planning on working on an IPv6 design in 2015?
http://arstechnica.com/business/2014/08/ipv6-adoption-starting-to-add-up-to-real-numbers-0-6-percent/
Sent from my iPad using Tapatalk
Large parts of China are IPv6 (makes sense as it was all built in the last 10-15 years).
Unfortunately Ipv6 suffers from the simple fact that for end-users (including enterprises) it makes no economic sense to use it until everyone else does.
Re: backward compatibility, I still have no idea why they didn't just double the freakin octets and make IPv4 addresses 0.0.0.0.x.x.x.x backward compatible. voila. You didn't even have to re-learn subnetting and hex. LOL
At my last job ~18 months ago, I was in the middle of provisioning IPv6 on one of our transit links, obtained my /32 from APNIC and had designed the subnetting. Then I jumped ship lol though I do remember at that time the number of queries we'd received re: IPv6 could be counted on one hand. Now I run ops for a variety of large enterprise customers and nobody is talking about it. At least in a SP role there was a definite impetus to stay ahead of the curve and not be caught with your pants down.
I, for one, prefer my service providers to wear proper trousers.
IPv6 addresses are amazingly unusable from an end-user perspective.
"Can you ping ten dot twenty dot seventeen dot one-twenty-one?" <- rolls right off the lips, easy to say and understand.
"Can you ping 2001:db8:85a3:0:0:8a2e:370:7334?" <- Wait, was that one :0 or two? Did you say db or bd or de or eb? Was that 8a2e or 8a2d? What? Can you read that back to me?
And heaven help explaining a double-colon in an address.
My experience with IPv6 has been to shut it down and not permit it to traverse the firewalls so that we wouldn't have someone creating Teredo tunnels to funnel out all our cool data.
We had plans to roll out in 2014, but they got put on hold because another major project blew up, and required a lot of extra work. We are looking at 2015 to have IPv6 running. Both our providers support it, and we have BGP peer with one, but are not advertising anything yet.
-Otanx
I'm still waiting for TWC to roll it out so I can test it at home. Lol
We were supposed to roll it out to the user community last year, but then found out, that some of they way we do stuff, rendered the Sup32's on 25 6509-E chassis obsolete, something about the Sup32's will not support 15.x code. so until the people that handle the money can budget for 25 Sup2T's we're in a holding pattern. (we just upgraded 75 4506 switches at another location)
The only place I've seen ipv6 implemented is on my cell phone lol
I guess if you are unlucky enough to be pigeon holed into a position with a cell phone carrier you might get some exposure.
Quote from: hizzo3 on February 17, 2015, 11:13:36 AM
I'm still waiting for TWC to roll it out so I can test it at home. Lol
Setup a tunnel to HE. I've been using it for about 6 years.
https://tunnelbroker.net/
Quote from: wintermute000 on February 17, 2015, 12:36:46 AMRe: backward compatibility, I still have no idea why they didn't just double the freakin octets and make IPv4 addresses 0.0.0.0.x.x.x.x backward compatible. voila. You didn't even have to re-learn subnetting and hex. LOL
http://tools.ietf.org/html/draft-chimiak-enhanced-ipv4-00
Thanks for the link, srg... that looks like a really cool thing.
Quote from: javentre on February 17, 2015, 12:52:44 PM
Setup a tunnel to HE. I've been using it for about 6 years.
https://tunnelbroker.net/
I did this and found some very weird things with Windows 7 and ipv6, so I ended up removing the tunnel. I found that Windows 7 although it's supposed to prefer IPv6 over v4, there were times where Windows 7 would just not use it. This was a while ago though so I should set it back up again.
Do you have specific examples?
I found out that removing IPv6 from a Windows 7 box (or 8) will severely mangle how it does its thing on the network.
Quote from: deanwebb on March 10, 2015, 08:25:22 AM
I found out that removing IPv6 from a Windows 7 box (or 8) will severely mangle how it does its thing on the network.
And you should (almost) NEVER uninstall the "Client for Microsoft Networks" from a NIC. Just uncheck it from the NIC, so it's not bound, but don't uninstall it. If you ever need to reinstall it, the success rate is less than 100%. This was an issue years ago, and they have support docs on how to fix it, but nothing for Win 8. I was forced to reinstall.
Is RA flooding still an issue on Windows?
https://samsclass.info/ipv6/proj/flood-router6a.htm
Always wanted to test it but never got to it
I have not seen much interest on IPv6 from the "normal" enterprise world but I think many if not most carriers/ISP already has some form of adoption with IPv6. Also I know some universities are fully IPv6 also in their core.
I noticed the new 8.0.110 WLC code is IPv6 ready though we don't use it so not sure how stable it is.