What happened to pub-vrs server. Temporary down or.....?

Kick me now. I'm probably not explaining myself terribly well. I have a flightaware dongle that works fine and is a receiver in VRS and feeds ADSBx no problem ( not now as I'm cleaning up the antenna and renewing the coax and boxing up my dongle to get it closer to the antenna socket and powering it POE) . What I am trying to say is that my experience with the Pi is uber limited and confined to the one time I set it up for FlDigi. I would rather feed to ADSBx and receive feeds from ADSBx via VRS as it is plug and play. I should have been clearer when I said Linux Noob, I mean I am having difficulty making it work and following the scripts method as the nomenclature isn't what I'm used to etc. What I am saying is, everything was going along fine this end as it was. It hasn't worked out so well your end and i get that. I was just thinking that it would be easier to wait until the status quo returns than persevere with the Pi which for me is one step forward two steps back. If I have to go the Pi way, then so be it, just hoped it would just all return to normal.

 

A pi is a much more power efficient, stable, and just an overall better way to do ADS-B reception.

The Pi just runs, you connect VRS, or whatever to it to look at planes.

How far is your coax run? People make a big deal about putting the dongle way up near the antenna, but it's not needed.

You burn and image to a SD card.
You edit the adsb-config.txt in notepad.
Plug everything into the Pi and it just works.

If your coax run is less than 50 feet, don't worry. It's far better to keep the Pi indoors.

 

Understood and thanks. I am mounting the dongle and filter closer to the antenna, the PC/Pi whatever remains inside fed by a USB to Cat converter at each end of a 60 foot run of Cat 6 cable (POE style). I am at altitude so I get from Lands end to Manchester and all points in between, but I did a test a while ago and mounting the dongle and filter close to the antenna makes a considerable improvement on longevity of signals received and a subjective improvement in range. I'll have another go at the Pi. Which Pi image are you referring to? The instructions on the script refer to "At a minimum, you will need a Pi running any Raspbian image that has dump1090 already installed." The link just takes me to the Raspian site.

 

https://www.adsbexchange.com/downloads/adsbx-v1.28vlan.zip

Use this image.

Make sure the ADSBXNAME is only letters and numbers .. not goofy shit.

Be aware of the sign of the decimal latitude and longitude, 4 places is sufficient - there is no need to point to an atom.

Altitude is assumed meters from sea level.

2.4GHz Wifi works out of the box. 5GHz you need to set country code.

I'm working on a new image release. It's almost ready and takes care of the B+ WiFi issues.

adsb-config.txt

Code:

LATITUDE 53.3661
LONGITUDE -2.6941
ALTITUDE 1100

ADSBXCUSTOMPORT 30005
ADSBXNAME "dual-pi"

ENABLE_WIFI yes
WIFI_SSID "SupaWifiADSB"
WIFI_PASSWORD "muchofun"
KEY_MGMT "WPA"

#################
#DEFAULTS BELOW
#DO NOT CHANGE
#UNLESS NEEDED
#################

MLATADSBXSERVER "feed.adsbexchange.com:31090"
ADSBXCUSTOMURL "feed.adsbexchange.com"

COUNTRY GB

REMOTE yes
PRIVACY no
MLAT yes
DUMP yes
UPDATE no
ENABLE_BT no
SHELLBOX no
UAT yes
UATPORT 30005
CELLULAR no

 

Ok, that looks like fun, I'll give it a whirl on the weekend . Thanks James.
My Pi 3B+ wont know what hit it, there hasn't been so much activity on it for years.

 

Dear to James. Please any update you can declare to on this issue of original topic?

Data stream to feeders on pub-vrs server.

Thanks to all who sharing data.

 

The problem is very tough to reconcile.

We found several commercial sites stealing the TCP feed and using it for commercial purposes. One was reselling it.

Honestly I don't have solution to pub-vrs , no other ADS-B site with the coverage and tech of ADSBx provides a global stream of data like we do.

FlightAware doesn't do it.
Flightradar24 doesn't do it.
Nobody does it.

Just today I was informed of a somewhat new commercial ADS-B site that was plugged into the TCP posing as a 'feeder' and funneling the traffic into a commercial site selling $500 a month subscriptions.

ADSBx partners and volunteers work hard to get feeds in some really cool places - so when that data shows up elsewhere at the same time it does on ADSBx something has to be done.

I don't know what the ultimate solution is.

It was a free for all mess, now since too many pissed in the pool. The pool is closed until we figure out a solution.

To be honest, I think many people were spoiled when Dan first started the site and offered the full feed back to them while paying for it all on his credit card. Had he not offered the TCP feed to feed an instance of VRS then nobody would be bemoaning it's demise.

 

Can you open it up again only to active peoples IP address who share 24/7 data to adsbx?

No share in = no stream out.

You know how adsbhub.org does this. I know you clever guys make this work.

Thanks to all who share. Shame those who spoiled this pool now. Close site except to adsb feeders & damn to leechers who do nothing.

Thank you for hard works.

 

You're missing what happened. I reopened it and the 3rd guy that was a 'feeder' that I gave access to was a commercial business selling ADSBx data. As soon as I turned him on the data came back then when I turned it off -- the data went away.

I don't give a shit what ADSBhub.org is doing. The data is garbage. If it's so fucking great why aren't you using adsbhub.org data? Because it's shit.

Who is paying for ADSBhub.org? I know what it costs to run ADSBx .. you think it's free?

Adsbhub.org don't reply to my emails. Fuck them. It's probably funded by a hedge fund or some other asshat wanting to sell ADS-B data.

You probably feed FlightAware and FlightRadar24 too? Go ask them for a global TCP data stream of 10Mbit/s ... Do it ... see what they say ...

 

Again I don't have a solution to this issue. I remove the firewall and 100's of connections come in over the TCP feed.

Having an IP check that you have a feeder really won't prevent abuse. We are going to figure out something but at this point .. I have no idea what that something is.

 

If I am understanding right that the core reason you can't support those 100s of connections is the huge cost of the bandwidth, then would you use a tool that supported those 100s of connections in a distributed way? Your servers would only have to push out a few copies of the stream and do some book-keeping to coordinate and keep everyone honest. Each node that received data from your servers would be responsible for forwarding it on to a small number of other servers, and so data would eventually fan out to everyone.

I started implementing such a thing a while ago but kind of dropped it, but I would totally finish that up if this site would use it. (This forum won't let me post a link, but github dot com slash PeterReid slash adsb-broadcast-client )

 

No, the server it's on uses a golang relay system and load balancer and has a 10Gbit pipe.

The problem is the data is valuable because FA charges $100K a month for what we give back to feeders for free; commercial businesses, other ADS-B sites, corporations, hedge funds, and who knows who else thinks the can do what they want with it if they just pretend to be an enthusiast feeder.

One of the guys I recently gave access to is relaying ADS-B data from ADSBx to a private equity funded site that was built to data mine ADS-B data.

I appreciate those that donate, and everyone who feeds. But the simple fact is donations account for 1-1.5% of what it costs to run ADSBx. We need to clamp down on the the abuse now - or nobody will be get data.

If every person using ADSBx donated $1 a month this really wouldn't be an issue. Which is why I think we need to put the map and everything behind a paywall.

Take ADSBx private and concentrate on making the best platform for those that enjoy it.

If you want to see all the planes and the data everyone provides then use the map like EVERY OTHER ADS-B SITE.

FlightAware doesn't give you a custom global data stream.

FlightRadar24 doesn't give you a custom data stream.

FOUND THE TWITTER AND GOT THEM BANNED FOR IMPERSONATION AND CONTROL OF THE ACCOUNT IS NOW UNDER ADSBx.

https://twitter.com/adsbexchange


If you want to write something, write something that connects to the REST API and outputs in VRS format, so these people can feed their local VRS and we can track who's using it 24/7 to figure out if they are an average person or a commercial business selling ADSBx data without supporting the project.

I really don't want to turn it back on, because people insist on feeding FlightAware, FR24, etc - ADSBx gives back 10 times what those sites do and people still have the audacity to bitch and moan when they can't get a 10Mbit/s data stream of every plane in the world back to their VRS.

Go ask FlightAware or FlightRadar24 to feed your VRS will a global data stream of aircraft for no cost and not monitored.

 

@PeterReid That's interesting.

https://github.com/PeterReid/adsb-broadcast-client

We did built a relay in Golang.

https://github.com/adsbxchange/tcp-relay-pub-vrs

Takes one stream and listens from incoming connections. Relays to many.