Mac OS X Problem Puts Up a Block To IPv6 204
An anonymous reader lets us know of an experiment conducted in Norway to determine real-world problems in using IPv6 today (Google translation; Norwegian original). "According to a Norwegian article in digi.no, Redpill Linpro did an experiment with regard to IPv6 on one of the largest online newspapers there (www.vg.no). They added a hidden iframe that pointed to an IPv6-enabled domain to test real-life problems about the reported IPv6 holes. The result was that mainly Mac OS X, older versions of Opera, and a few Linux distributions exhibited problems. For Mac OS X it took 75 seconds to time out before failing back to IPv4." From the consultant's report: "Mac OS X has a problem in that it will prefer 6to4-based IPv6 over IPv4-based connectivity, at least if its local IPv4 address is an RFC 1918-based private address as commonly found in NAT-ed home network environments. This is unfortunate, as 6to4 has shown itself to be much less reliable than IPv4."
Chicago (Score:5, Funny)
Chicago? (Score:3, Funny)
Is this a Chicago [wikipedia.org] reference by the Mac OS X dev team?
Re:Help me understand this. (Score:0, Funny)
Fuck you asshole
Fuck you too.
Seems like some people need to go to AAA(Anonymous Assholes Anonymous) meetings.
normal person + anonymity = asshole way too often.
Comment removed (Score:2, Funny)
Re:ugh, apple get with the program!!! (Score:0, Funny)
I see it as a two birds one stone sort of scenario.
Advantage 1 - Upgrade the internet have more IPs for everyone.
Advantage 2 - Stop Macs from polluting our internets with their gay Metro-sexual; Prius driving; Jobs loving; Turtleneck sweatery asses.
Re:Chicago (Score:5, Funny)
I just got off the phone with some one of my connections in Apple's product development department.
Apparently the math required to implement IPv6 uses far too much battery and processor resources so Jobs opted to abandon its implementation.
Re:John C. Randolph, give us the real story. (Score:5, Funny)
Disregard that, I suck cocks.
-jcr
Re:John C. Randolph, give us the real story. (Score:3, Funny)
You're sexy when you talk tough.
Re:Chicago (Score:5, Funny)
Apparently the math required to implement IPv6 uses far too much battery and processor resources so Jobs opted to abandon its implementation.
And it's not shiny, maybe one day they'll implement it as iPv6
Here's a quick solution, say in a Flash? (Score:5, Funny)
75 seconds by Apple web-browsing standards sounds like a long time. I seem to recall Mr Jobs pointed out that Flash is the only thing responsible for slowing down the Web on a Mac. Now, I have an iMac G5 and Flash doesn't slow down my experience by 75 seconds. So intstead of changing the TCP/IP stack in OSX, or fixing Safari, I think what would please Apple (in getting faster experience on the Web for the customers) would be to ask Adobe to make a Flash IPV6to4 wrapper for their TCP/IP stack.
I don't even know if this would even be possible, in fact I don't think it is. I leave the challenge to Adobe, and the PR to Apple to explain how Adobe fixed their 'problems'!
I have already accepted I used at least 75 seconds of my web browsing experience to write this post!
Re:John C. Randolph, give us the real story. (Score:3, Funny)
You're sexy when you talk tough.
Not as sexy as you are when you put on that big funny hat, Your Holiness.
Re:Not so simple (Score:3, Funny)
The root cause here is multipath confusion, but there are lots of other ways the transition will get bumpy.
Once the IPv4 address exhaustion wave starts to break, the Internet community is going to be dealing with all manner of breakage caused by some parts of the Internet resisting the transition to IPv6 while other parts are being forced into the transition by financial considerations. These different parts will be intermediated by things like NAT64 and DNS64, as well as other evils like DS-Lite and the associated AFTR boxes. Meanwhile, there will still be crazy things like 6to4 and Teredo kicking around. For the transition to go smoothly, all these interlocking parts have to work perfectly... everywhere... and we know from long experience that this just cannot happen.
This will all seem fairly familiar to anyone who survived the transition to IPv4 a generation ago. But if you're a young gun, and all you've ever known is the IPv4 we have now because the old-timers spent a long damned time years and years ago making it rock-solid before you got here, then you're about to be schooled.
Get ready for life during wartime—that's what I say.
Re:Chicago (Score:3, Funny)
5) "..and Boom!"
Re:Why would /. focus on OSX problems?... (Score:3, Funny)
Linux as a whole gets halfway there with each passing year. I'm sure they'll eventually make it all the way.
(Wish I could find a link to the math problem I'm thinking of)