I have a question about what am I seeing when I display the WEB Interface: View Live Data option. The display is divided into two sections: Left - Map with tracked aircraft, Right - Dump 1090. I realize that this data is coming from FA’s server and I am going to assume that this represents the traffic that my receiver is seeing and inputting. If this is correct then my Pi does not buffer the data and it is sending the reports as they are received, FA then processes the reports and outputs them to the Live Data View screen. Please let me know if this is what is the process is.
You have about a 50/50 distribution between adsb and MLAT aircraft.
The adsb aircraft go straight into the GUI/Web interface.
The MLAT data is sent to FA, process and returned to your RPI and fed into the GUI/Web interface.
It is possible to view adsb aircraft with no Internet connection.
MLAT requires MLAT servers. It is possible to setup your own, however, you would need 3+ receivers setup in a triangular pattern. They would also need to be far enough apart for the data to be useful.
Around 2020, the majority of powered aircraft in the US will be transmitting adsb, either on 1090Mhz or 978mhz, These transmissions will include location data.
I didn’t really give you enough information to reply to my question. I don’t have a monitor with a HDMI port near to my RPi. I am using a windows web browser on a remote PC to get the feed. If I could get the software to work on a Ubuntu desktop I wouldn’t have this issue.
Sorry, I don’t understand the question.
What are you asking for? dump1090 should be able to display webpages to any device on your network.
I view it from my laptops, desktop and ios devices.
I guess I did not know that I could send the Dump1090 output to other devices on my network. Is there instructions on how to do this, if not then I have some additional reading to do.
The “view live data” page is actually your feeder Pi–it is a small webserver running on your Pi. The map and the aircraft list show positions as they are received by your radio.
The only data from FA on the live page is the MLAT positions. You could even disable your FA account and that live page would still work (except you’d have no MLAT data).
Thanks guys, I just got it. When I sign into the Web Interface I am actually signing into the Pi port:8080 which I can prove by looking at the properties of the web display url. Now it makes sense, I thought that FA was providing the web data back to me for the display. I couldn’t figure out how Jon was getting the data to display on his network without going to FA. Just sign on to the Pi’s local address port 8080.
It’s possible to view the data on your pi aware remotely (outside of your local area network) by using port forwarding. I’ve done this using my own setup. I won’t publish the URLs, though, since I don’t want to flood them with requests.
I initially went this route but I couldn’t get comfortable with the network security. My solution was to set up a PPTP VPN and forward port 1723. It’s still not the greatest security but I can get onto my home network and connect to Raspberry Pi’s and webcams.
I don’t know that much about port forwarding. Can you explain what the risk is, if I designate a port to go to my piaware port 8080 for http requests only?
My understanding is that the risk is low but the specific vulnerability would most likely be an exploit in the web server software. If you’re using lighttpd and it’s kept up to date and it’s properly configured, the risk is minimized. If you’re using the dump1090 built-in web server, I have no insight into the vulnerabilities. I go straight to using lighttpd on my installs and it’s been a long time since I messed with the built-in web server.
In my case it was also beneficial to set up a VPN because this is how I use it when I’m not at home:
-Viewing the dump1090 web pages on my Pi’s
-Viewing my server webpage that has webcam pics, temperature sensors, and whatever else I’m playing around with at the time
-Accessing my Pi’s remotely (I use xrdp/Remote Desktop Connection but VNC does the same thing)
-Accessing the Internet from public or open WiFi hotspots with better security
PPTP VPN is pretty easy to set up on a Pi compared to OpenVPN but the trade-off is apparently less security. I follow the VPN tutorial on raspberrypihelp.net for my VPN setup and use duckdns for free DNS resolution to my external IP. I enable the VPN on Macs and IOS devices and presumably it would work just fine with Windows or Android since it’s a standard protocol.
How does the myADSB page compile its information? Specifically the IP address of the internal interface. I have looked at the page code but its not obvious how that information is compiled. I assume the link 192.X.X.X:8080 is being generated when the page is being created but how does the pc that is running the browser “discover” the IP addy of the piaware RPi?
Guessed as much, thanks. Is there a way to block that, as I assume FA don’t need that info to display data from my site? I know that you can’t get to it without logging into my profile but…still seems like an unnecessary vulnerability.
Not only don’t others see it, even if they did see it they would not be able to access it unless they were connected to your local LAN, if it is a 192.168.n.n address. 192.168.n.n is non-routable. That means a request for that address can’t flow over the internet. The end point has to be on the same LAN as the requester. (i.e. In your house, or nearby if on wifi.) There are some other non-routable addresses too, but I don’t remember exactly at the moment. I think 10.n.n.n is another one.
The local addresses are part of RFC1918.
192.168.x.y, 10.x.y.z and 172.[0-32}].X.y plus another one or two.
The end point doesn’t technically have to be on the same lan. I have a VPN to two other Networks and it could be on any of those.
It just needs to be on a network that I have a route and access to(and return)
