We are going see how this goes. The reason VRS format TCP went away for the majority users was there was 350 'users' connected 24/7 365 days a year. Many were corporate, data center, commercial internet ip addresses, and there was too much abuse. There were several ADS-B sites selling the aggregated data, selling services around ADSBx data, or just using the feed to promote their plane spotting site without crediting ADSBexchange.com or even asking to use it. None of them were supporting or crediting ADSBx. Those that did, a few of them lied about usage and eventually got caught. There was drama and then more drama. Lot's of temper tantrums and nasty emails making threats to not feed ADSBx from VRS unless they get the global feed back - trust me, no loss there as VRS feeds are statistically very low quality. TCP was also shut down because spending hours emailing and supporting people running VRS on a Pi trying to consume the feed or trying to use TCP and feed from VRS on the Pi was not on the list of things I needed to focus on. Fast forward after writing a bunch of code, and getting things working. Therefore ... You must meet the requirements at https://adsbexchange.com/data/. To get access, you need to have a Pi receiver or other reliable device like radarcape, etc.. No exceptions. You cannot feed from VRS. NO VRS FEEDERS. NO EXCEPTIONS. Your receiver sending data to ADSBx needs to have reasonable range and reliability. ADSBx takes a lot of time and effort to make it all work - it's appreciated if you do that same if you want the global data stream. Your Internet needs to be able to handle the data stream, it's requires at least a 25Mbit download, 100Mbit preferred. You need to be able to receive and process all the data before the server sends you the next data burst. If you can't then the server will disconnect you and eventually ban your IP. Home users with dynamic IP that does not change often can use TCP. Most ISP now days keep your IP for a while, so this should work for everyone. TCP Stream Once you have a Pi feeder or other reliable device like radarcape, etc. Verify it works by using curl or opening a web browser from the same IP as feeder. https://adsbexchange.com/myip/ Contact me on the forum or email [email protected] and attach this information. I will verify feeder, and open firewall for your VRS from your IP. Remember if your Internet connection can't handle the live data stream then your IP will be banned. You can possibly prevent this by using UDP. See below. UDP Stream If you have a server / remote VRS with static ip or DNS, UDP should be used. You will need to setup a listener and port on your server. ADSBx will broadcast over UDP to your server port. If you are a home user and understand how to open a port / forward a port, then ADSBx appreciates if you use UDP. Experienced Linux based users can code a listener, or use socat. Example with VRS running on PC with LAN IP 192.168.1.125 with receiver waiting for connection in AircraftJSON format on port 32005 Create a script called vrs-receive.sh Code: #!/bin/bash while true; do socat udp4-listen:5000 tcp4:192.168.1.125:32005,fork,forever sleep 2 done After this is setup then email me your servers Static IP or DNS url. ADSBx send a stream to your remote server port. It is advisable you only accept data from ADSBexchange.com pub-vrs IP on this port using a firewall. Looking forward to see how this goes. James ADSBx
Well, that was short lived. Some jackass crashed the server overnight by building up a huge TCP queue. Is there something in the water? I really pray that stupid isn't contagious ...
