Dear,
I read carefully the “Connecting to external ADSB data sources” section of sdr-enthusiasts/docker-adsb-ultrafeeder, but I can’t find out how to get my setup tuned.
Because of shadowing by obstacles (walls) me and a friend are running two instances of ultrafeeder, 400 m away from each other. I will also offer a restricted web access, he will not open any inbound ports on his firewall. So the concept is: he will send his beast+mlat data to my instance, my instance will join both. I am fine with all the DNS and firewall tasks. The thing I don’t understand is: which of our instances need what two lines in the ULTRAFEEDER_CONFIG section?
Say, Alice and Bob owning DNS names alice.example.org and bob.example.org, where Alice is collecting all and Bob is only sending Beast and Mlat.
I’d expect, Alice in addition needs to map ports 30004 and 31004 in docker-compose.yml, nothing else.
Bob must only add this line:
ULTRAFEEDER_CONFIG=mlat,alice.example.org,30004;mlat,alice.example.org,31004
Is this by chance right?
Because Alice already sending to a number of enthusiasts and planefinder, adsbhub and opensky, I am afraid of accidentially creating loops or wrong data. Thus, I fear to “just try and observe”.
Only send data to an extra instance that doesn’t feed any aggregators.
Also it would be:
adsb,asdf,40004,beast_out
mlathub,asdf,41004,beast_out
with protocol beast_out.
Just create an extra instance on your side that doesn’t talk to an SDR.
Deconflict the ports via compose yml.
On your SDR instance and his instance, add the config to push the data.
Ah, okay. Surprisingly a complete different concept, but quite safe.
If I got it right, I’ll need 3 ultrafeeder instances in total:
one at Bob, no web UI exposed to public, just SDR as input and sending adsb+mlat
one at Alice, no web UI exposed to public, just SDR as input and sending adsb+mlat
a third one at Webster. He does not send to anyone, is not handling a SDR, but is exposing his 8080 web port.
Perhaps it’s better to run Webster on his own hardware, because MLAT precision could get affected from high load at the Raspi3? I’ll need to do some performance observations.
Right. Good to point this out to me! I read this a few weeks ago but then forgot about it. After reading your comment, I found some warnings in the logs, so I reduced the load on my Docker.
For the main project (marking the distance of neighboring aircraft on railway noise diagrams) I may skip MLAT for now. Our noise measurement is especially important at night. The only effect of MLAT in my area is seeing all the Piper and Cessna aircraft that don’t appear to have night flying equipment. If we also need to differentiate between rail and aircraft noise during the day on Saturday, we can then adjust the setup to Pi4/5.
