> On Jan 16, 2018, at 11:05 AM, Jens Alfke <j...@mooseyard.com> wrote: > >> On Jan 16, 2018, at 2:11 AM, Quinn The Eskimo! <eski...@apple.com >> <mailto:eski...@apple.com>> wrote: >> >> The fact you’re using a legacy API like this implies that you’re not >> IPv6-compatible. To can learn more about this is my “Supporting IPv6-only >> Networks” pinned post on DevForums. >> >> <https://forums.developer.apple.com/message/136166#136166 >> <https://forums.developer.apple.com/message/136166#136166>> > > According to Stuart Cheshire(?)’s talk at a recent WWDC, some cell carriers > have switched their data networks over to IPV6-_only_. This may be the cause > of the problem. Even if gethostbyname is able to retrieve an IPv4 address for > your server, your device would be unable to send packets to it because > there’s no IPv4 router upstream.
Jens, Quinn, I have verified that I can indeed access the server via cell data using NSURLSessionDataTask & friends. So yes, it appears that trying to go through IPV6-only networks using IPV4 APIs doesn’t work very well… BSD sockets were sure fun. But this means heavy rewrites of *lots* of legacy code, apps, and servers... Ugh. Thanks for the help! -Carl
_______________________________________________ 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
