Now that I’ve moved and I’m reliant on a satellite internet connection vs a “normal” setup, I’ve noticed that my connection back to FA is fraught with inconsistent connections. I lost my streak (180 days) and now it goes down every once and awhile with the TLS handshake issues. While that’s happened with FA, I feed FR24 with the same setup and I haven’t lost a beat other than when I moved the device.
Any comments?
I would try piaware-mutability. It seems to keep retrying. I’m not sure if he added in a feature to handle that, or…
that’s what I’m running…
Sadly, satellite internet service has a pretty long lag time. Every bit of data you send has to travel 35,000 Km up to the satellite, then back down to the ground. The receiving end then sends back up to the satellite and then it’s back down to you - 140,000 Km round trip - and that’s not counting how far the receiving end has to transmit and receive from FlightAware. You might do better if you can get DSL service at your house. I had a satellite ISP called Starband - for two weeks. I dropped it as soon as realized the truth about the time lag.
I’m quite aware of the latency with satellite and if there was any other (DSL included) I would have it.
The question remains, why is fr24 much more forgiving of the latency whereas piaware isn’t.
Can you paste some logs from when the problem is occurring?
05/20/2015 12:01:18 connecting to FlightAware 70.42.6.203/1200
05/20/2015 12:01:19 error during tls handshake: handshake failed: connection reset by peer, will try again soon...
05/20/2015 12:01:59 7885 msgs recv'd from unknown-port-30005-process via unknown-port-10001-process (115 in last 5m); 6752 msgs sent to FlightAware
05/20/2015 12:02:40 connecting to FlightAware eyes.flightaware.com/1200
05/20/2015 12:02:42 error during tls handshake: handshake failed: connection reset by peer, will try again soon...
05/20/2015 12:03:42 connecting to FlightAware 70.42.6.203/1200
05/20/2015 12:03:44 error during tls handshake: handshake failed: connection reset by peer, will try again soon...
05/20/2015 12:04:48 connecting to FlightAware eyes.flightaware.com/1200
05/20/2015 12:04:50 error during tls handshake: handshake failed: connection reset by peer, will try again soon...
05/20/2015 12:06:09 connecting to FlightAware 70.42.6.203/1200
bump
bumping again… this time with the ping to eyes.flightaware.com. I can see it… and yeah… the latency is significant. Which leads me to the question of why is FR24 so much more forgiving of the latency than FA?
pi@piaware ~ $ ping eyes.flightaware.com
PING eyes.flightaware.com (70.42.6.203) 56(84) bytes of data.
64 bytes from eyes.flightaware.com (70.42.6.203): icmp_req=1 ttl=49 time=729 ms
64 bytes from eyes.flightaware.com (70.42.6.203): icmp_req=2 ttl=49 time=699 ms
64 bytes from eyes.flightaware.com (70.42.6.203): icmp_req=3 ttl=49 time=710 ms
64 bytes from eyes.flightaware.com (70.42.6.203): icmp_req=4 ttl=49 time=724 ms
64 bytes from eyes.flightaware.com (70.42.6.203): icmp_req=5 ttl=49 time=678 ms
64 bytes from eyes.flightaware.com (70.42.6.203): icmp_req=6 ttl=49 time=727 ms
^C
--- eyes.flightaware.com ping statistics ---
7 packets transmitted, 6 received, 14% packet loss, time 5999ms
rtt min/avg/max/mdev = 678.800/711.671/729.519/18.128 ms
Might be handy to see a tcpdump while it’s broken:
$ sudo apt-get install tcpdump
$ sudo tcpdump -n -i any icmp or tcp port 1200
(leave it running while some reconnect attempts happen, control-C when you’re done)
There seem to be issues with connecting to FA in any manner for anything?
pi@piaware ~ $ sudo apt-get install tcpdump
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libpcap0.8
The following NEW packages will be installed:
libpcap0.8 tcpdump
0 upgraded, 2 newly installed, 0 to remove and 24 not upgraded.
Need to get 549 kB of archives.
After this operation, 1,184 kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Err http://flightaware.com/mirror/raspbian/raspbian/ wheezy/main libpcap0.8 armhf 1.3.0-1
Connection failed
Err http://flightaware.com/mirror/raspbian/raspbian/ wheezy/main tcpdump armhf 4.3.0-1+deb7u2
Connection failed
Failed to fetch http://flightaware.com/mirror/raspbian/raspbian/pool/main/libp/libpcap/libpcap0.8_1.3.0-1_armhf.deb Connection failed
Failed to fetch http://flightaware.com/mirror/raspbian/raspbian/pool/main/t/tcpdump/tcpdump_4.3.0-1+deb7u2_armhf.deb Connection failed
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
pi@piaware ~ $
I can fetch those URLs ok from here. Can you reach them from a web browser? (If yes: there’s something odd with your Pi. If no: there’s something odd with your entire connection…)
“Server unexpectedly dropped the connection…”
What ports do I need to have forwarded on my router other than 10001 and 30005?
You shouldn’t need to forward any ports at all, there aren’t any inbound connections required.
If you can’t access the raspbian packages from a web browser, I would be extremely suspicious about what your ISP is doing. Maybe they have a badly behaved transparent proxy that is breaking things.
(This can also be caused by various “antivirus” / web filtering / censorship “features” that some routers and ISPs provide. Turn them all off if you can)