Connectivity Problems Affecting Us All
I think we all are experiencing the same 15-25 sec gaps. The simple answer, like FR24 Support told Gerry, is a connectivity problem between us and the MLAT server at wro.fr24.com, half a world away.
If you use the ping program builtin to your operating system to ping -t wro.fr24.com you will see what the firmware in the receiver is experiencing when trying to call home to the MLAT server. After an few failures the firmware tries to heal itself and reconnect until it succeeds in pinging the MLAT server.
Unfortunately, since we all have the same transit to the server, our latency (ping time) is close to 500 ms in the best of times.
The MLAT server is not the same server as the one ads-b traffic is directed to from your receiver. Pinging the ads-b server at IP 83.140.21.89 has timeouts also.
It's just my humble suggestion that FR24 custom upgrade the software in our receivers to call home to the Australian servers which were put in place to overcome problems like these in Australia and New Zealand. Our routing goes through Australia anyway.
If you have updated the software in your receiver, you may have noticed that the build date reported in the log is not what you thought it should be after updating. There are builds in August, October and December. The act of rebooting the receiver either through the Status Page or a brownout rolls back the version to the August build.
Also the seeming non-fatal error libcommon read_config failed - /etc/fr24feed.ini is common during the update process.
This is all I know so far..which isn't much..but I humbly don't know everything.confused.png
John
F-RPVD1
Dumaguete
Originally posted by gquejada
View Post
If you use the ping program builtin to your operating system to ping -t wro.fr24.com you will see what the firmware in the receiver is experiencing when trying to call home to the MLAT server. After an few failures the firmware tries to heal itself and reconnect until it succeeds in pinging the MLAT server.
Unfortunately, since we all have the same transit to the server, our latency (ping time) is close to 500 ms in the best of times.
The MLAT server is not the same server as the one ads-b traffic is directed to from your receiver. Pinging the ads-b server at IP 83.140.21.89 has timeouts also.
It's just my humble suggestion that FR24 custom upgrade the software in our receivers to call home to the Australian servers which were put in place to overcome problems like these in Australia and New Zealand. Our routing goes through Australia anyway.
If you have updated the software in your receiver, you may have noticed that the build date reported in the log is not what you thought it should be after updating. There are builds in August, October and December. The act of rebooting the receiver either through the Status Page or a brownout rolls back the version to the August build.
Also the seeming non-fatal error libcommon read_config failed - /etc/fr24feed.ini is common during the update process.
This is all I know so far..which isn't much..but I humbly don't know everything.confused.png
John
F-RPVD1
Dumaguete
Comment