Skip to content
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

Issues with setting up external adsb receiver #134

Open
JayBraker opened this issue Oct 17, 2022 · 1 comment
Open

Issues with setting up external adsb receiver #134

JayBraker opened this issue Oct 17, 2022 · 1 comment
Assignees

Comments

@JayBraker
Copy link

Hi, I have dump1090 (not dump1090fa) running on the host, exposing its interface to 0.0.0.0:30002
Installed this container with

extra_hosts:
  - "host.docker.internal:host-gateway"
 environment:
  - BEASTHOST=host.docker.internal
  - BEASTPORT=30002
  - RECEIVER_TYPE=relay

Which makes the feed available on host host.docker.internal:30002
However piaware does not ingest, writing "framing errors seen, is the peer sending Beast binary data?" to the log.
I assume faupload1090 (gets mentioned in the logs, unfortunately not at all documented) would need to be reconfigured to connect to my receiver.

Does anyone have experience with this kind of issue?
Feeds for fr24 and adsbx run flawlessly

@mikenye
Copy link
Member

mikenye commented Feb 5, 2023

Try port 30005.

@mikenye mikenye self-assigned this Feb 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants