You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
Describe the bug
Description is from this downstream bug report:
To Reproduce
See subject.
Expected behavior
-6 should only enable IPv6 and not disable IPv4.
Operating system
FreeBSD 14.2
The text was updated successfully, but these errors were encountered: