-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MLAT in relay mode #89
Comments
Hi @ZeeBOB, sorry for the delay in getting back to you about this. When using the container in relay mode (with
As Would you accept me adding an |
Hi @ZeeBOB, I've added:
These control the # If MLAT_RESULTS_BEAST_CONNECT is specified
if [[ -n "$MLAT_RESULTS_BEASTHOST" ]]; then
piaware-config mlat-results-format "$(piaware-config -show mlat-results-format) beast,connect,${MLAT_RESULTS_BEASTHOST}:${MLAT_RESULTS_BEASTHOST:-30104}"
fi Will be merged in #124. |
Once PR #124 is merged, this issue will automatically be closed. After this, the new image will build (will take about 1-2 hours). Once complete, please pull the image and update your container. Please feel free to re-open the issue if you're still having problems after that. Thanks. |
I'm running dump1090-fa on a remote machine. When I have this container in relay mode MLAT is unable to connect, probably because it's trying to connect to dump1090-fa on localhost:30104, as per the Multilateration Settings on FlightAware's Advanced Configuation page:
If the container is in relay mode, it should reuse the BEASTHOST variable and add the following line to the piaware.config file:
mlat-results-format beast,connect,$BEASTHOST:30104
I'm guessing this is best done in the docker-piaware/rootfs/etc/cont-init.d/01-piaware file
piaware-config mlat-results-format "beast,connect,${BEASTHOST}:30104"
The text was updated successfully, but these errors were encountered: