Dump1090 serves on port 30005 right??

FlightAware ADS-B Flight Tracking
1

Hi everyone,

I’m happily serving data to flightaware using OpenSuse and an RTL-SDR dongle. Dump1090 talks to faup1090, which also happily talks to piaware and the flightaware servers.

The issue is that even though faup1090 is clearly receiving data on port 30005 from dump1090, it also reports that there is no ADSB program broadcasting on port 30005. See this output (lat and long redacted!):


05/13/2017 07:33:45 ADS-B data program 'dump1090' is listening on port 30005, so far so good
05/13/2017 07:33:45 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat XX.XXX --lon X.XXX
05/13/2017 07:33:45 Started faup1090 (pid 2617) to connect to dump1090
05/13/2017 07:33:45 piaware received a message from dump1090!
05/13/2017 07:33:46 piaware has successfully sent several msgs to FlightAware!
05/13/2017 07:34:16 283 msgs recv'd from dump1090; 283 msgs sent to FlightAware
05/13/2017 07:34:44 failed to run netstat: 

child process 2650 exited with status 4
05/13/2017 07:34:44 no ADS-B data program is serving on port 30005, not starting multilateration client yet

After this point, the messages from the last 4 lines cycle through every minute, with the msgs received count increasing as expected.

I’m wondering whether dump1090 isn’t pushing mlat data properly (how would i check that?) or whether there’s a port address switch I’ve not assigned correctly in some config file somewhere.

To get this working this far on OpenSuse has been a battle. I’ve had to compile everything from source and basically put everything in the right place manually…

2

05/13/2017 07:34:44 failed to run netstat:
child process 2650 exited with status 4

piaware wants to run netstat via sudo (so it can use -p to identify the processes owning listening ports); you’ll probably need to configure your system to allow that to suppress the error.
Probably piaware needs to be a bit more careful in its error handling here so that it doesn’t prevent mlat from starting if it can’t run netstat.

To get this working this far on OpenSuse has been a battle. I’ve had to compile everything from source and basically put everything in the right place manually…

Given that it’s not a platform that we explicitly support, that’s not unexpected. If you’re willing to do the packaging work, you can send a pull request for the piaware_builder repository and I can integrate those changes.