3 ms·
I'm not discounting the article's assertions, but we're doing fine with a ~7,000 node IPv4/IPv6 network. Each node is running a reasonably modern client OS (80
by runjake 16y ago
I'm not discounting the article's assertions, but we're doing fine with a ~7,000 node IPv4/IPv6 network.
Each node is running a reasonably modern client OS (80/20 Mac OS X/Windows 7, mostly). Most of our servers are Windows Server 2008 and some 2003. We do have several Linux servers, as well. Pretty much all the service they run seamlessly translate to IPv6 (Exchange, IIS, SMB, AFP, Apache [and its modules])
Each node and server get an IPv4 address and an IPv6 address. Mac OS X and Windows prefer IPv6 transport over IPv4 and most users have no clue when they go to Google, they're doing so over IPv6. nearly all of our internal web, email, and file sharing traffic is over IPv6. Nobody knows any different. There has been small, interesting issues, but we're able to resolve them pretty quickly and haven't run into anything even marginally major.
From the looks of things, the transition will be like the fader control on an audio mixer. Nodes will have dual stacks, and IPv4 will fade out gradually and IPv6 will, at the same time, fade in gradually, and nobody will be the wiser (other than the poor network programmers who have to get their network code IPv6 ready, which frankly, they should've begun years ago).
Implementing a large-ish scale IPv6 network (dual stacked, of course) has been relatively pain-free (in our experience).
- tptacek 16y agoI think the subtext of this article is that schemes like this appear to work because you're really relying on IPv4 for guaranteed network access; the true migration to IPv6 (the "magic moment" as DJB would call it) hasn't happened until people can feasibly not depend on IPv4 for a production network. If everyone has to be dual-stacked, then we're committed indefinitely to making IPv4 workable. Which is fine! But it rather lessens the urgency of converting people to IPv6.
- runjake 16y agoBut are we really relying on IPv4 when at least 90% of our network traffic has seamlessly transitioned to IPv6? It's almost funny to say this, but it seems like IPv4 is already legacy for us. Sure, some external websites haven't yet converted to IPv6, so the stack falls back to IPv4, but for the most part (and 90% is probably a very conservative estimate) IPv6 is king across the WAN. The downside to IPv6 is that it's a steep learning curve, and virtually nobody else in the org is even marginally familiar with it. If you're familiar with bit math, IPv6 is a bit easier, but then you get into routing and DHCPv6 which tend to differ significantly in some areas from their v4 counterparts. Also, I'm finding that certain vendors' (cough Cisco) IPv6 implementations aren't nearly as tight as they claim. It wasn't until July 2010 that Cisco really implemented DHCPv6 in a usable manner in IOS. Now if only Apple iOS devices supported IPv6 ;)
- ay 16y agoIPv6 on iPhone 4: http://www.fix6.net/archives/2010/06/22/ipv6-on-iphone/ http://www.fix6.net/archives/2010/06/22/ipv6-on-iphone/ For the learning: take a look at http://www.6deploy.eu/index.php?page=tutorials http://www.6deploy.eu/index.php?page=tutorials - they seem pretty nicely readable, maybe you can use those materials. Curious about the 90% part - care to tell more over mail ? If yes - then ay at the general direction of your cough ;-)