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

readsb's --net-bind-address is not configurable / does not listen on IPv6 #284

Open
duckfullstop opened this issue Jan 17, 2024 · 1 comment

Comments

@duckfullstop
Copy link

duckfullstop commented Jan 17, 2024

I appreciate this is probably a little more of an edge case, but I'm rocking docker-readsb-protobuf on an IPv6-first Kubernetes cluster. As services are advertised primarily by their IPv6 address, and this container forcibly sets --net-bind-address to 0.0.0.0 (the IPv4 catchall), anything that tries to dial this container over IPv6 just gets turned away at the door.

Simple proposed solution: Make READSB_NET_BIND_ADDRESS a configurable value overruling this line here:

READSB_CMD=("--net-bind-address=0.0.0.0")

and potentially consider setting the default to ::, as almost all systems should tolerate it (?), and it should also bind to the wildcard v4 address at the same time.

(if readsb doesn't support binding to :: then by all means close this issue - that's the main reason I haven't done a PR!)

@wiedehopf
Copy link
Contributor

Consider running https://github.com/sdr-enthusiasts/docker-adsb-ultrafeeder
It should listen on ipv4+ipv6.

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