Piaware 2.1-3 is now available. You can update via the ADS-B stats control panel, or by manually installing the updated packages.
The default port for multilateration results has changed
Piaware now sends mlat results to port 30104 by default. This change is to try to avoid accidentally feeding mlat results to a dump1090 that is not mlat-aware and may forward the results on unexpectedly (e.g. to other feeder software that doesn’t expect to see them).
If you are using the Flightaware-provided dump1090, please update your dump1090 package as well as updating piaware. The updated dump1090 package has a corresponding change and you don’t need to do anything special.
If you are using a different dump1090 and want to continue to forward mlat results to it, you will need to reconfigure either piaware or dump1090. To reconfigure piaware to use the older default of port 30004:
$ sudo piaware-config -mlatResultsFormat beast,connect,localhost:30004
$ sudo service piaware restart
Alternatively, you can reconfigure your dump1090 to accept data on port 30104 by passing “–net-bi-port 30104” on the command line.
If you do either of these, please be sure that whatever dump1090 feeds on to is expecting to see mlat results, or that you are running a mlat-aware dump1090 that doesn’t forward the results on.
If you’ve previously changed the piaware mlatResultsFormat option, that setting overrides the default already and you shouldn’t need to touch it.
Mostly bugfixes and minor tweaks. Full changelog is here. Main user-visible changes:
Avoid ever running two copies of piaware (with the same pidfile, at least)
Fix piaware-status in non-English locales
Additional logging in fa-mlat-client to report more details of how well multilateration is working.
Detect problems with the UDP traffic used by multilateration (if there is a problem, you’ll get some log messages & an anomaly on the stats page)