October 13, 2010 09:16
Well, that was a success!
I changed the DNS to 8.8.8.8. iNavX (v 3.1.7 now) went through about two-thirds of the East Coast charts before timing out again. This is a vast improvement. (I tested right before the change to make sure the bug was still active; it was--couldn't download anything.)
The view from the wifi router indicated very little packet traffic during the time out (haven't had time to do any analysis yet).
This looks to be consistent with a DNS failure: iPad sends a DNS request; no packet returned; iPad waits >30sec to retransmit; iNavX times out; firewall doesn't flag the traffic because it's just DNS traffic. That makes perfect sense.
Thank-you for the suggestions.
Maybe the workaround should go in the FAQ, since it is likely to affect all iPads.
Might also be worthwhile either adjusting that time out value or making it user settable; sailors end up sticking their resolvers into some strange domain name servers!
I changed the DNS to 8.8.8.8. iNavX (v 3.1.7 now) went through about two-thirds of the East Coast charts before timing out again. This is a vast improvement. (I tested right before the change to make sure the bug was still active; it was--couldn't download anything.)
The view from the wifi router indicated very little packet traffic during the time out (haven't had time to do any analysis yet).
This looks to be consistent with a DNS failure: iPad sends a DNS request; no packet returned; iPad waits >30sec to retransmit; iNavX times out; firewall doesn't flag the traffic because it's just DNS traffic. That makes perfect sense.
Thank-you for the suggestions.
Maybe the workaround should go in the FAQ, since it is likely to affect all iPads.
Might also be worthwhile either adjusting that time out value or making it user settable; sailors end up sticking their resolvers into some strange domain name servers!
iBoat
'05 490 Meridian
No Court
'05 490 Meridian
No Court