

If you examine the FlightAware flow disgram, you will see that normal sharing data is received from modesmixer2 on port 30005, the same port used by PlanePlotter and ppup1090 for autonomous uploading to PlanePlotter servers. 01:52:11 5746 msgs recv'd from modesmixer2 (1872 in last 5m) 5746 msgs sent to FlightAware 01:51:46 mlat(2313): Server: 2.7 kB/s from server 0.0kB/s TCP to server 10.0kB/s UDP to server 01:47:11 3874 msgs recv'd from modesmixer2 (1902 in last 5m) 3874 msgs sent to FlightAware 01:42:11 1972 msgs recv'd from modesmixer2 (1831 in last 5m) 1972 msgs sent to FlightAware 01:37:59 server is sending alive messages we will expect them 01:37:11 141 msgs recv'd from modesmixer2 141 msgs sent to FlightAware 01:36:45 piaware has successfully sent several msgs to FlightAware! 01:36:45 piaware received a message from modesmixer2! 01:36:41 multilateration data requested, enabling mlat client 01:36:41 multilateration support enabled (use piaware-config to disable) 01:36:41 logged in to FlightAware as user donf99 01:36:41 Started faup1090 (pid 2311) to connect to modesmixer2 Code: 01:36:41 ADS-B data program 'modesmixer2' is listening on port 30005, so far so good
