undefined | Better HN

Skip to content

Top Best Ask Show New Jobs

0 pointsloeg7y ago0 comments

Do you have more detail on how collection messes with MLAT calculations? It seems like for triangulation purposes, each device should produce some precise timestamp that is not affected by store-and-forward transmission.

0 comments

5 comments · 2 top-level

theyinwhy7y ago· 3 in thread

Unfortunately, there is no good solution for this. Either you rely on the time settings of the sender or on the time needed to transmit the data and on the time the data gets transmitted.

wbl7y ago

A radio receiver with a GPS time base doesnt seem that tricky.

lmz7y ago

If we assume the sender is not malicious, a properly configured NTP client ("the time settings of the sender") would probably suffice. If the sender is malicious, unless you somehow make the "signal + timestamp" from the receiver non-modifiable from the receiver to the service, you've lost anyway.

toomuchtodo7y ago

Because MLAT relies on multiple devices, it should be straightforward to identify and blacklist a sender tampering with timing data.

I don't think the programs are made to handle that use case. At present you register your receiver's location with the server once and send packets as they arrive, that server doesn't know that your packets are from multiple receivers at multiple locations.

https://discussions.flightaware.com/t/aggregation-of-dump109...

https://github.com/mutability/mlat-client

j / k navigate · click thread line to collapse