-
Notifications
You must be signed in to change notification settings - Fork 260
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
Implement IPv6 to IPv4 fallback #1208
Comments
I'm doing this 🖐️. I just need to source format the changes and send the PR. It's working locally now (tested by starting the server from the command line and connecting from I've implemented it like this:
However, I'm still allowing the But if you think it's better to remove it I can try to do it. |
Merged and will be part of 2.3.4 - @3hhh FYI.
Agreed. Thanks again! |
Nice! Thanks to @ivan-zaera! |
* commit '683270db64302e59d26b9610514af1cfe0a80493': Bump to 2.3.5 Fix libinstpatch and sndfile not being discovered on Windows (FluidSynth#1299) Update FreeBSD CI: Drop 12.4 and add 14.0 Fix some rounding issues due to double promotion (FluidSynth#1286) Bump to 2.3.4 Fix player termination after stopping and restarting (FluidSynth#1273) fix for issue FluidSynth#1268: Pipewire's Jack implementation not found (FluidSynth#1269) Fix issue with CMake Xcode generator (FluidSynth#1266) Refurbish CI (FluidSynth#1267) Fallback to IPv4 when creating socket if IPv6 is not available (FluidSynth#1208) (FluidSynth#1265) Turn off pending notes and issue a warning (FluidSynth#1264) Fix incorrect way of turning CMAKE_INSTALL_LIBDIR absolute (FluidSynth#1261)
Related discussion
#1205
Is your feature request related to a problem?
The
enable-ipv6
cmake option disables IPv4 support, causing fluidsynth's server to fail starting on system which have disabled IPv6 runtime supportDescribe the solution you'd like
Ideally, get rid of the
enable-ipv6
option altogether. This can be done byEAFNOSUPPORT
use an IPv4 socket.Describe alternatives you've considered
none
Additional context
Low priority issue, contribution required.
The text was updated successfully, but these errors were encountered: