Hi, So new to feeding to ADSB Exchange, and I've done something wrong.. I'm sending multiple feeds! /myip/ is showing: Data incoming from: xx.xxx.125.228 Route: MLAT_front Port: 31090 Backend: MLAT_back_3 Connected: mlat-c Age: 3h57m Data incoming from: xx.xxx.125.228 Route: CustomFeeds_500 Port: 51360 Backend: custom_51360 Connected: cons_30005 Age: 3h57m When I then look on monitoring of my firewall I can see a whole load of streams sending out. Is anyone able to help and advise where I can look in the config to work out how I managed to set up so many streams and stop it, not sure anyone's going to want to get so many streams from me!
And let's check: pgrep -fa adsbexchange pgrep -fa socat Looking at the firewall picture again, it could well be it's just a single stream, but due to reconnects the firewall shows multiple connections over the last 24 hours. (Or what timeframe is that output from?) Or rather it's the normal connection for ADS-B traffic and a second connection for MLAT. (If you wonder why it's adding up to more than 24h) Doesn't mean it's multiple connections at the same time. Your rc.local looks correct anyway.
Thanks, the firewall flow is over 24hrs, I had it feeding to flightaware and radar24 before and traffic level was around 150Mb per day, suddenly up to over 600Mb per day. Output of those two commands is: Output from Netstat on the device giving the details of each of the streams running: Thanks Richard
That's all correct. fr24feed and other feeders condense the data quite a bit before transmitting them. adsbexchange is fed with all ADS-B and ModeS messages and condenses the data down on the server side. (opensky-network uses this method also but they even keep every single message in their enormous database) As you can see from the pgrep output, only one socat is running for feading beast on 30005. That takes quite a bit of volume. Then there is the mlat client which is separately connecting to adsbexchange, that's also perfectly normal. Your firewall then doesn't of course know that it's the same program after a reconnection because it seems to be sorting by source instead of destination port. So if you check all the connections to adsbexchange in your firewall list and add up the active time, it should be 48 hours for the 2 connections
OK, thats good news, and the uncompressed bit makes sense with the amount of data, it was just such a big jump, and appeared to be so many open connections, more importantly didn't want to be sending loads of duplicate data and causing issues! Cheers for help checking, much appreciated!
https://adsbexchange.com/myip/ I correctly working connection will show both a connection to beast and mlat. The firewall thing is likely MLAT server connection, connecting then disconnecting, the reconnecting ... they will fall off .. that's just MLAT server code Oliver stopped developing it when FlightAware hired him. Same with dump1090.
