Re:Apple under fire for backing off IPv6 support
by rbarooah on Friday April 13, 2012 @12:22PM
(#3837472)
Thankfully Apples 'action' isn't true.
All that's happened is that they released a new style Airport Utility, with a simpler UI that doesn't support IPv6 yet.
They are still supplying a version with IPv6 support, and presumably a point release will add it to the new style utility soon enough.
Re:Apple under fire for backing off IPv6 support
by nolok on Friday April 13, 2012 @11:44AM
(#3837258)
> The article says Comcast will be first ISP to provide IPv6 to residential customers.
In the US. We've had native IPv6 with Free (3rd biggest ISP) in France since January 2008, and I wouldn't be surprised if other ISP elsewhere did it even sooner.
The article says Comcast will be first ISP to provide IPv6 to residential customers.
But my AT&T DSL modem gets an IPv6 address from AT&T, and it assigns IPv6 to client computers via DHCP, and my client computers (Mac, Linux, Windows) all accept the IPv6 addresses. And I'm able to ping to IPv6 addresses.
All out of the box.
I actually faced an interesting problem because this OOB IPv6 support was being used by a few programs, unbeknownst to me. Some website (IIRC, related to python's pip) was sending both IPv6 and IPv4 addresses via DNS.
And curl was following spec and trying to download from the IPv6 address first. This had apparently been going on without my noticing for a long time without problems.
Until I attached a half-assed wifi-to-ethernet bridge (Asus WL 330GE), which didn't support IPv6. My client machine still got the IPv6 addresses via DHCP, so curl tried to download via IPv6, but alas, the packets never made it to my router.