I believe current Rechability classes are not supporting ivp6 address. Hence, wondering if Apple is going to release new version for it as all app have to be compliant with ivp6 address?
Is Apple going to release new version of Reachability classes to support IPV6 address?
What are you using reachability for? I'm finding it hard to imagine a situation where you'd want to run a reachability probe on a IPv6 address specifically (as opposed to a DNS address, which the Reachability sample code already shows how to do).
Share and Enjoy
—
Quinn "The Eskimo!"
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"
We are using reachabilityForLocalWiFi from reachability class? I notice reachabilityForLocalWiFi method is using reachabilityWithAddress (local ip address)? I am wondering how will it work for the ivp6 address? Currently it works for ipv4 address.
I don’t think that will be a problem. Even if the device only has IPv6 connectivity to the outside world, it should still be able to get to link-local IPv4 addresses (169.254/16), which is what
+reachabilityForLocalWiFi uses.
Have you tried this in the IPv6-only test environment that we introduced at WWDC?
Share and Enjoy
—
Quinn "The Eskimo!"
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"
We use reachabilityForInternetConnection method to check connectivity. The method uses struct sockaddr_in. According to Apple's documentation, struct sockaddr_in6 should be used for IPv6.
So the question is though current Reachability classes may work in IPv6 testing environment but should the code be eventually updated for IPv6 compatibility? I plan to upgrade my MacBook to OS X 10.11 and setup local IPv6 network to test whether Reachability 3.5 works with IPv6 or not.
I have tested Reachability class [1] in NAT64 environment, and doesn't crash. But I am not sure it will work correctly in the real world.
I hope Apple release a new version of Reachability. Many third party libraries use it and it is a de facto standard.
It's little bit confusing that Apple's document [2] is pointing out the flaws of the Reachability sample code.
[1]
[2]