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

jamulus-server: -6 makes server IPv6 only on FreeBSD #3478

Open
yurivict opened this issue Feb 10, 2025 · 2 comments
Open

jamulus-server: -6 makes server IPv6 only on FreeBSD #3478

yurivict opened this issue Feb 10, 2025 · 2 comments
Labels
bug Something isn't working
Milestone

Comments

@yurivict
Copy link

Describe the bug

Description is from this downstream bug report:

Adding -6 to the jamulus_server_flags does enable IPv6, but drops the socket for IPv4.

I believe this is due to different defaults between Linux and (Free)BSD. The code opening the socket should specify the correct flag to get a socket that supports both IPv4 and IPv6.

To Reproduce

See subject.

Expected behavior

-6 should only enable IPv6 and not disable IPv4.

Operating system

FreeBSD 14.2

@yurivict yurivict added the bug Something isn't working label Feb 10, 2025
@github-project-automation github-project-automation bot moved this to Triage in Tracking Feb 10, 2025
@softins
Copy link
Member

softins commented Feb 10, 2025

Thank you for the report. There is some relevant information from an unrelated project here.

It would appear it is possible to configure a FreeBSD system to support IPv4-to-IPv6 address mapping in the same way as it works under Linux, Windows and macOS, but that on OpenBSD that possibility does not even exist, deliberately. At present, it is impossible to determine how many xxxxBSD Jamulus servers there are in public directories, because they will report their OS type as Linux. However, I suspect the number is very small. I don't believe any of the core developers uses a BSD variant.

It looks like the proper way to solve it portably would be to have separate sockets for IPv4 and IPv6 within the Jamulus application. That won't happen in the 3.x series of Jamulus releases, but we can consider it for Jamulus 4.0, for which significant enhancements to IPv6 support are planned. There is no timescale yet.

@ann0see ann0see added this to the Release 4.0.0 milestone Feb 10, 2025
@ann0see
Copy link
Member

ann0see commented Feb 10, 2025

Definitely not good. Can we at least add some documentation somewhere?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Triage
Development

No branches or pull requests

3 participants