Redirecting Piaware 3.3.0 to remote Virtual Radar Server VRS

FlightAware ADS-B Flight Tracking
1

I’d like to take the stock SD image install for Piaware and do the following… but am not clear on how best to do this…

Fork 1090 data to port xxx0 on remote VRS server
Fork MLAT data to port xxx1 on remote VRS server
Fork 978 data to port xxx2 on remote VRS server

Everything appears to be running great locally… I just need to break it out and send it to a waiting VRS server that is already listening on those specific ports for this data.

Thank you in advance!
:question:

2

dump1090 does not forward messages to other servers, it only listens to incoming connections (both for input and output).

You’ll need something like modesmixer2 to mix/forward your data. The easieast way would be set up VRS to connect to dump1090

3

Config Step 1 - Connect ADSB 1090 Mhz data on Pi to VRS on remote server.
For ADS-B, the default port for format “Basestation” is 30003, and for “AVR or Raw Beast Feed” is 30005
https://farm6.staticflickr.com/5725/31177870625_99e2d3ce4a_o.png

Config Step 2 - Connect MLAT data on Pi to VRS on remote server.
For MLAT, the default port for format “Basestation” is 30106, and for “AVR or Raw Beast Feed” is 30105
https://farm6.staticflickr.com/5733/30370811993_f140bbabf5_o.png

Config Step 3 - connect UAT 978 data on Pi to VRS on remote server: Same as step 1, but use port number you have configured Pi for 978 uat.

Config Step 4 (optional) - prepare a merged feed if you want to display combined streams like adsb+mlat+uat
https://farm6.staticflickr.com/5667/30810625430_230dc59700_o.png

4

Use ModeSmixer. Use it 3 times, one for each port if you want to keep them separate all the way to VRS, it works just fine.

EDIT: And in VRS you enable “push” receivers.

/M

5

Or socat.

6

Can any one explain why to use modeSmixer2 (or any other method) when:

(1) dump1090/dump978 make data available at ports 30003, 30005, 30105, and 30106.

AND

(2) VRS is capable to connect to, and get data directly from dump1090/dump978 on Pi.

7

It can be easier to do connections from the receiver outbound towards a VRS server located elsewhere if the receiver is behind NAT or a firewall or has an unpredictable address, but the VRS server isn’t so restricted.

8

How? I was trying to use /bin/nc 127.0.0.1 30005 | /bin/nc/ myvrs.com xxxxx for the 1090 feed

9

Oh! I am sorry. I misunderstood that both the Pi and VRS Server are on the same LAN.

Your approach should work provided
(1) The remote sever running VRS is configured to accept external connection at port xxxxx
(2) The remote sever running VRS does not require authentication/login by incoming connection.

If your remote server requires authentication/login, you can do this by curl
To do this:

  1. Create a new file
    sudo nano connect.sh
  2. Now copy-paste following code in this file, and save this file


#! /bin/sh
while true
  do
    sleep 30
    curl --user USERNAME:PASSWORD http://www.myvrs.com:xxxxx -v
    /bin/nc 127.0.0.1 30005 | /bin/nc myvrs.com xxxxx
  done

  1. Now make this file executable
    sudo chmod +x connect.sh

  2. Run this file
    sudo ./connect.sh &

Since I have placed argument -v at the end of curl command, you will get an output. It will be something like this



[1] 10831
 * Rebuilt URL to: http://www.myvrs.com:xxxxx/
* Hostname was NOT found in DNS cache
*   Trying zzz.zzz.zzz.zzz...
* Connected to www.myvrs.com (zzz.zzz.zzz.zzz) port xxxxx (#0)
* Server auth using Basic with user 'USERNAME'
> GET / HTTP/1.1
> Authorization: Basic YWJjZDU2N0Bob3RtYWlsbC5jb206YTFiMmMz
> User-Agent: curl/7.38.0
> Host: www.myvrs.com:xxxxx
> Accept: */*
>