dump1090 is not running.
faup1090 is running.
piaware is running.
dump1090-mutab is listening for connections on port 30005.
faup1090 is connected to port 30005.
piaware is connected to FlightAware.
dump1090-mutab is producing data on port 30005.
Check the piaware 2.1-3 thread. The standard port for back-feeding mlat positions to dump1090 has changed. Best to reconfigure your dump1090-mutability and specify beast listening port 30104 instead of (old) default of 30004.
No problem. But the thing with v1.14 is that it will pass on any mlat positions that it receives on 30104 as regular ADSB positions on port 30005. This may or may not be a problem, depending what else you are feeding from that instance of dump1090. Some other software and/or sharing sites may not like the mix of mlat and ADSB positions and complain about it. That’s why it’s best to use latest FA-supplied dump1090 or mutability v1.15~dev. Both are mlat-aware and will by default NOT forward mlat positions in their 30005 output.
So I’m getting around to building dump1090-mutability v1.15~dev. What’s the best way to go about changing from version 1.14 to 1.15? Is it necessary to ‘dpkg --remove dump1090-mutability’ before installing v1.15?