So let me clarify my question. (Yes I understand this is FA, PiAware, and Dump1090) I am asking the question more for the dump1090 port and formatting of data.
Your assumption is incorrect. I have the piaware image with no modifications done to it at all. I did not have VRS setup to receive any mlat data at all. I had a different post yesterday asking about all the ports Dump1090 uses and there function. http://discussions.flightaware.com/ads-b-flight-tracking-f21/what-ports-are-used-by-piaware-2-1-3-dump1090-t36069.html
30001 - Inbound - RAW Format
30002 - Outbound - RAW Format
30003 - Outbound - Base station Format
30004 - No Longer Used??? Unless you have it configured manually
30005 - Outbound - Beast format
30104 - Inbound - Beast format
4999-9999 - Outbound- UDP
My take away from the other post is that dump1090 receives mlat data from FA servers on port 30104 as of 9/28/2015 and uses it internally “only” displaying on the dump1090 web interface.
With that knowledge if I run the following command it should output mlat in beast format to port 30004 turning port 30004 from and inbound to an outbound port. As prior to 9/28/2015 it was looking to receive data on that port from FA.
Like “Kabuse” post I got the below results after running this command.
$ sudo piaware-config -mlatResultsFormat beast,connect,localhost:30004
10/02/2015 00:30:58 multilateration support enabled (use piaware-config to disable)
10/02/2015 00:30:58 multilateration data requested, enabling mlat client
10/02/2015 00:30:58 Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --results beast,connect,localhost:30004 --udp-transport 70.42.6.197:5348:3652216451
10/02/2015 00:30:59 mlat(2599): fa-mlat-client 0.2.4 starting up
10/02/2015 00:30:59 mlat(2599): Using UDP transport to 70.42.6.197:5348
10/02/2015 00:30:59 mlat(2599): Input connected to localhost:30005
10/02/2015 00:31:00 mlat(2599): Beast-format results connection with localhost:30004: [Errno 111] Connection refused
10/02/2015 00:31:07 piaware has successfully sent several msgs to FlightAware!
10/02/2015 00:31:30 mlat(2599): Beast-format results connection with localhost:30004: [Errno 111] Connection refused
10/02/2015 00:31:57 server is sending alive messages; we will expect them
10/02/2015 00:32:00 mlat(2599): Beast-format results connection with localhost:30004: [Errno 111] Connection refused
10/02/2015 00:32:31 mlat(2599): Beast-format results connection with localhost:30004: [Errno 111] Connection refused
10/02/2015 00:33:01 mlat(2599): Beast-format results connection with localhost:30004: [Errno 111] Connection refused
10/02/2015 00:33:31 mlat(2599): Beast-format results connection with localhost:30004: [Errno 111] Connection refused
10/02/2015 00:34:02 mlat(2599): Beast-format results connection with localhost:30004: [Errno 111] Connection refused
10/02/2015 00:34:32 mlat(2599): Beast-format results connection with localhost:30004: [Errno 111] Connection refused
10/02/2015 00:35:03 mlat(2599): Beast-format results connection with localhost:30004: [Errno 111] Connection refused
10/02/2015 00:35:10 680 msgs recv’d from dump1090 (626 in last 5m); 514 msgs sent to FlightAware
10/02/2015 00:35:33 mlat(2599): Beast-format results connection with localhost:30004: [Errno 111] Connection refused
10/02/2015 00:36:02 piaware (process 2166) is shutting down because it received a shutdown signal (SIGTERM) from the system…
10/02/2015 00:36:02 multilateration data no longer required, disabling mlat client
10/02/2015 00:36:02 removing pidfile /var/run/piaware.pid
10/02/2015 00:36:02 piaware (process 2166) is exiting…
10/02/2015 00:36:05 ****************************************************
Now looking at this log, I have a question.
Did I just tell “fa-mlat-client” to send mlat data to port 30004 like it did prior to 9/28/2015? I thought this command was telling dump1090 to send mlat data to port 30004 not “fa-mlat-client”
http://e0.flightcdn.com/adsb/images/diagram.png
Now after I ran this command
$ sudo piaware-config -mlatResultsFormat "beast,connect,localhost:30104 basestation,listen,31003"
I get this in the log file.
10/02/2015 00:36:06 Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --results beast,connect,localhost:30104 --results basestation,listen,31003 --udp-transport 70.42.6.197:5350:1647847444
10/02/2015 00:36:06 piaware received a message from dump1090!
10/02/2015 00:36:06 piaware has successfully sent several msgs to FlightAware!
10/02/2015 00:36:07 mlat(2707): fa-mlat-client 0.2.4 starting up
10/02/2015 00:36:07 mlat(2707): Using UDP transport to 70.42.6.197:5350
10/02/2015 00:36:07 mlat(2707): Listening for Basestation-format results connection on port 31003
10/02/2015 00:36:07 mlat(2707): Input connected to localhost:30005
10/02/2015 00:36:07 mlat(2707): Beast-format results connection with localhost:30104: connection established
10/02/2015 00:36:35 58 msgs recv’d from dump1090; 58 msgs sent to FlightAware
10/02/2015 00:37:05 server is sending alive messages; we will expect them
10/02/2015 00:39:07 mlat(2707): Accepted Basestation-format results connection from 10.0.0.131:53456
10/02/2015 00:39:07 mlat(2707): Basestation-format results connection with 10.0.0.131:53456: connection lost
10/02/2015 00:39:13 mlat(2707): Accepted Basestation-format results connection from 10.0.0.131:53471
10/02/2015 00:39:52 mlat(2707): Accepted Basestation-format results connection from 10.0.0.131:53577
Question how do I remove the 1st config telling it to look at port 30004?
Question what is going on with port 31003? what did i just tell it to do with that command? I do not understand all of the piaware-config commands I guess.
Notice I can care less about VRS or PP or any other program that uses the mlat data at this time. I just wanted to understand the who,what,why,when,where of the ports and there data. As any of the listed programs need to point to one or many of the ports in use.
OK so I talked with someone a LOT more knowledgeable about Linux than I .
I ran the following command and got back this
netstat -nap|grep "LISTEN"
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 2059/dump1090
tcp 0 0 0.0.0.0:30001 0.0.0.0:* LISTEN 2059/dump1090
tcp 0 0 0.0.0.0:30002 0.0.0.0:* LISTEN 2059/dump1090
tcp 0 0 0.0.0.0:30003 0.0.0.0:* LISTEN 2059/dump1090
tcp 0 0 0.0.0.0:30005 0.0.0.0:* LISTEN 2059/dump1090
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2242/sshd
tcp 0 0 0.0.0.0:30104 0.0.0.0:* LISTEN 2059/dump1090
tcp 0 0 0.0.0.0:31003 0.0.0.0:* LISTEN 2707/fa-mlat-client
Now that helps me understand that I told fa-mlat-client to open up a port not dump1090