October 9, 2010 23:56
Update: I installed Network Ping for IOS and pinged a host that does not exist on my lan (and therefore cannot possibly send reply packets).
Firewall IP popped up instantaneously when I sent a ping, but it does not do so with iNavX on the occasions that iNavX times out.
On the occasions that iNavX successfully downloads a chart, Firewall IP consistently asks if it is OK to make the connection, and, once affirmed, the chart downloads.
This is strong evidence that, while there may sometimes be a delay of more than 30 seconds contacting the NOAA server from my iPad, iNavX is, at times, not even trying to contact it.
I'll try to put a packet sniffer on the lan and have a look.
Firewall IP popped up instantaneously when I sent a ping, but it does not do so with iNavX on the occasions that iNavX times out.
On the occasions that iNavX successfully downloads a chart, Firewall IP consistently asks if it is OK to make the connection, and, once affirmed, the chart downloads.
This is strong evidence that, while there may sometimes be a delay of more than 30 seconds contacting the NOAA server from my iPad, iNavX is, at times, not even trying to contact it.
I'll try to put a packet sniffer on the lan and have a look.
iBoat
'05 490 Meridian
No Court
'05 490 Meridian
No Court