I would like to share my SkyAware map with my family overseas, to let them be able to see the aircraft I am directly detecting on FA. Especially for the younger ones, I think this would give them a more in-depth interest in what ADS-B can reveal, than describing to them just the setup I currently have (which they may well find fascinating in and of itself).
I’ve looked over the forums a little, but I did not see anything relevant in my searching (this may be from the search terms used, and not that the information is nonexistent on the forums).
Is there an easy way to share with others the SkyAware map, detailing the same as I can get in my browser via my local RPi IP?
A link I can send them would be ideal, but if there is some sort of tunneling required then I am up for that too (whether the adults overseas would view this with interest I have in accomplishing it, is a question I’ll broach with them another day).
Your device is operating the map via web interface. So you will need to open your local router to access from outside and use a DynDNS service in case your router is getting a new IP adress from your provider.
Then the visitors are using this DynDNS adress and (if set up properly) they have the same view than you.
Be aware that you can open your network to the public if you are not setting it up properly
Here is how I set up external access to a SkyAware map on my RPi.
In router map a port to port 8080 on your RPi - * 7003 to 192.168.1.50 8080 where
is for any incoming IP
7003 is the external port used to access the map
IP of the RPi
SkyAware port
(each router will have its own way of mapping a port)
From an external browser access the SkyAware map by entering
:7003
A final word of caution. If you have more than the RPi on your network you should isolate the RPi from the rest of your network. I do this by setting up a guest WiFi ssid for the RPi to connect to. A guest WiFi has full access to the internet but no access to the local network.
edit - I’m connected to my ISP via DHCP but my IP has not changed in over 15 years so it may as well be a static IP. My ISP requires a commercial account ($$$) for a static IP.
As already posted, at the simplest you can just port forward and give your family the IP & port number. The problem here is that if your IP address changes you’ll need to send another link. DynDNS would fix this.
My setup uses a reverse proxy and Dynamic DNS to give me a nice looking link…
Personally, I don’t think opening ports and port forwarding is considered safe anymore. There’s just too many risks beyond your control over time. Did you have a look at this thread: Remote DUMP1090/978 access via website?
For personal use I created this page. Last year I downloaded dump1090 extracted files locally then uploaded some of them to a website host. Then created a stripped down version of dump1090’s index.html and other js config changes. Then created a monitored process on my RPI to ftp aircraft.json to my web host to /public_html/dump1090/data folder every 7 seconds. There are far better ways to upload tiny files frequently, but 7 second ftp puts works well enough.
It’s hacky and stripped down, but aircraft.json is a tiny file to upload frequently. I can see planes with positions move on the map every 7 seconds and mouse hover over them to see the basic stats. Message rate updated in the tab title every 7 seconds. It’s been working for about a year. Good practice to make sure file references to lat/lon location details are a little off from reality when you share your station to the public.
Using readsb together with tar1090 can make the trick as well. @wiedehopf is providing a script which install it on any device.
readsb is a replacement for dump1090-fa and can be easily configured in net-only mode.
So if you have a remote server (VPS is ok) you can simply install it there, forward the data via an outbound connect to that server and you will have the same view as on the Raspberry.
If the forwarded end is firewalled, why not? Like forwarding the router port to access to my Linux machine that hosts the Piaware map. I turned on the UFW on that machine.
The problem is you then have to trust the security of the service you have forwarded the port to. It’s much safer to put the service behind a reverse proxy based on something well known with a lot of active security development rather than forward connections directly. Many home served services use their own web server implementation and are therefore a bit of an unknown quantity.
That’s true. But then, we need to have trust in something.
So I have a port from my router being pointed to the Linux computer running the tar1090 webpage port. I trust that the tar1090 doesn’t have any undocumented “features” to leak that access into my network.
You’re really trusting lighttpd, tar1090 has little to do with its security.
nginx might be better for that purpose, tar1090 provides config files for nginx though user action is required to include those in an nginx config.
