MLAT not synchronised but connected?

Thanks Oliver, I guess that means this thread is effectively dead now :smiley:

…well, actually, possibly not!

I’ve noticed a recurrence of a connection problem since 17:38:14 yesterday.
I get this repeated about every 5 minutes…

@obj should I reboot my raspberry Pi(s) to pick up a new configuration following the rebalancing?

Perhaps I am still pointing at stale addresses? I certainly have no network problems for other applications, despite the “check your network” NOTICE from adept server.

UPDATE:
I’ve just looked in my /var/log/piaware.log and suspiciously it appears that around time 17:38 it looks like fa-mlat-client started up a transport connection to cetgu.hou.flightaware.com [70.42.6.224] for the UDP

In one way I’m surprised I’m not connecting to a more local node (for me 20 hops, min 106 ms), but I’m hardly unsurprised that I am seeing "multilateration messages (UDP) are not reaching the server " with such a long route being used. Is this a case of: Houston, we have a problem ? :wink: