> On Nov 11, 2014, at 8:43 AM, Josh Graessley <jgraess...@apple.com> wrote: > > Reachability is not meant to be used prior to connection (not a pre-flight > check). If you don’t check reachability first and just try to connect, does > it work?
[I'm the developer of the framework the OP is using; the framework API doesn't provide a way to disable reachability checks.] Could you elaborate? I've been using the SystemConfiguration reachability API in various incarnations for a long time (since iChat I think) and I've tended to use it as a preflight, i.e. wait for the green light from reachability before trying to open a connection. After all, my understanding is that if an address is said to be unreachable, that means that there is no active network interface that knows how to route packets toward that address, so it's not worth attempting to connect because opening a socket would just fail immediately. Right? And although I haven't been able to reproduce this failure myself, the symptom appears to be that a ".local" hostname on the local subnet (obtained from Bonjour) is reported as unreachable, which seems unambiguously wrong. —Jens
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to arch...@mail-archive.com
