@barjac:
I had the same problem/error with my feeder some weeks ago ("[mlat][w]Could not ping MLAT server, result=-1000, ..."). At that time, for testing purposes, I also "bent" the mlat-1.fr24.com to 52.20.254.84 (which is mlat-2.fr24.com) in /etc/hosts and this worked well, exactly how you reported. I then contacted support (support@fr24.com) and told them about it. Some days later my problem was gone. Meanwhile I had a new problem, which is also gone (for details see http://forum.flightradar24.com/threa...6643#post86643). Currently my feeder is working as it is supposed to.
Looking at all these uncomfortable "events", I come to the conclusion, that noticed MLAT problems are - partly - specific to the individual feeder (T-*****). Maybe the FR24 guys have a "critical" look on new MLAT feeders for data quality reasons and consequently don't give "full MLAT permission" immediately to new feeders. However, this is my personal speculation, not more.
Good luck, -Wolli-
I had the same problem/error with my feeder some weeks ago ("[mlat][w]Could not ping MLAT server, result=-1000, ..."). At that time, for testing purposes, I also "bent" the mlat-1.fr24.com to 52.20.254.84 (which is mlat-2.fr24.com) in /etc/hosts and this worked well, exactly how you reported. I then contacted support (support@fr24.com) and told them about it. Some days later my problem was gone. Meanwhile I had a new problem, which is also gone (for details see http://forum.flightradar24.com/threa...6643#post86643). Currently my feeder is working as it is supposed to.
Looking at all these uncomfortable "events", I come to the conclusion, that noticed MLAT problems are - partly - specific to the individual feeder (T-*****). Maybe the FR24 guys have a "critical" look on new MLAT feeders for data quality reasons and consequently don't give "full MLAT permission" immediately to new feeders. However, this is my personal speculation, not more.
Good luck, -Wolli-
Comment