piaware MLAT Client with wrong configuration for Beast-format results connection and http feed tracker dosn´t show any airplanes about docker-fr24feed-piaware-dump1090 HOT 7 OPEN

PR are welcome. 😄
I did not do it because not enough time and no need for it. Also it's a bit tedious to do it for all feeders.

from docker-fr24feed-piaware-dump1090.

I you want to connect to a remote dump1090, you can do it like that:

      - "DUMP1090_ADDITIONAL_ARGS=--json-location-accuracy 2 --net-bi-port 30004,30104 --net-only"
      - "SERVICE_ENABLE_IMPORT_OVER_NETCAT=true"
      - "DUMP1090_LOCAL_PORT=30004"
      - "DUMP1090_REMOTE_HOST=dump1090"
      - "DUMP1090_REMOTE_PORT=30005"

If you do it like this, you don't have to change anything else.

from docker-fr24feed-piaware-dump1090.

I you want to connect to a remote dump1090, you can do it like that:

      - "DUMP1090_ADDITIONAL_ARGS=--json-location-accuracy 2 --net-bi-port 30004,30104 --net-only"
      - "SERVICE_ENABLE_IMPORT_OVER_NETCAT=true"
      - "DUMP1090_LOCAL_PORT=30004"
      - "DUMP1090_REMOTE_HOST=dump1090"
      - "DUMP1090_REMOTE_PORT=30005"

If you do it like this, you don't have to change anything else.

Ok that is weird. In my opinion the mlat client of piaware should also use the environment var PIAWARE_RECEIVER_DASH_HOST and maybe a additional env variable like PIAWARE_RECEIVER_DASH_BEAST_PORT for the port definition - like in the other feeder parts.

I mean the same issue exist also in the ADS-B Exchange feeder. There both XXXX_RECEIVER_HOST and XXXX_RECEIVER_PORT variables are missing and the feeder also try´s 127.0.0.1

Everything is working fine if dump1090 is running in the same container, but if it runs outside - like on my side - some of the feeder will not work, which is a shame, because it is a relly nice deployment/package which you created.

But back to your answer, it means that your dump1090 starts and takes the input from my dump1090 outside and forwards it to the mlat client, right?

If so - not a nice setup . Is there not the possiblity to provide the external receiver var for host and port to all feeder´s and also to the "secondary" parts of the feeder - like the mlat client of piaware ?

Anyway, I will try - but in my opinion not the best solution

from docker-fr24feed-piaware-dump1090.

It might be possible to do it the way you want.
But this image was made to put everything in the same place.
Routing the traffic from remote dump1090 to the local one is the easiest way I found, it avoid complex configuration and works pretty good, it's just two dump1090 taking to reach other.

from docker-fr24feed-piaware-dump1090.

It might be possible to do it the way you want. But this image was made to put everything in the same place. Routing the traffic from remote dump1090 to the local one is the easiest way I found, it avoid complex configuration and works pretty good, it's just two dump1090 taking to reach other.

But why then the environment var exist for XXXX_RECEIVER_HOST and XXXX_RECEIVER_PORT on other feeder´s section´s ?
I mean yea your image was build for single container which is mostly perfekt and when docker swarm compose will fully supported devices like USBs, then everything will be fine for me ;) - but at the moment they don´t support it.

I mean, is it really a high risk to replace every 127.0.0.1 defintion with a environment var for every feeder section ?
It would be a complete implementation rather than just a partial one and it gives more flexibility.

Yea it is work i know but one point more for your image ;)

from docker-fr24feed-piaware-dump1090.

So no chance that you will fix that point - that every 127.0.0.1 address for actually local dump1090 app / or feeder section, is more flexible to set via env var for a remote instance ?

from docker-fr24feed-piaware-dump1090.

No chance right now sorry. It would involve some rework and documentation, I'm pretty sure people won't use it properly in the end.

For me using local dump1090 connecting to a remote one it a solid workaround for now. It's how I've been using it for several years.

from docker-fr24feed-piaware-dump1090.