-
Notifications
You must be signed in to change notification settings - Fork 827
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
IP_MULTICAST_IF fails #990
Comments
Thanks @ericeil for reporting this. We already have a task tracking the work required for supporting 'IP_MULTICAST_IF'. We don't have an ETA at the moment. |
I would like to bump this as well - running into exactly this issue running https://github.com/UltraMessaging |
@sunilmut Is there anything new about this one. Thanks for the hard work. |
@makpac - Apologize for the delayed response.
No, not yet. It's in the pending list. Just curious, is this blocking any scenario for you? |
@sunilmut, I tried to install and run a server app which use multicast to talk to its clients and it sets IP_MULTICAST_IF as a socket option. It's not a blocking me as ended up installing it on a VM but being able to run the app on the same machine and without using VMs would be super cool. :) |
Just an update that support for IP_MULTICAST_IF and IPV6_MULTICAST_IF has been checked in the dev branch and should soon make it to the release branch. |
Hello All, |
@bbidault2 - Yes. If you keep an eye out on our release notes, we usually publish what's available in an Insider build. We are a bit slow in getting the release notes out for this release, will have it out soon. Apologize for the delay. Regarding the support for 'IP_MULTICAST_IF', it should come out soon. Thanks for trying WSL! |
Here is the release note for build 16170. Thanks @jackchammons |
This should be fixed in Insider build 16176. |
On rs_preview build 14905:
The following works on Linux, but fails in WSL:
.NET Core has support for setting the multicast interface by either address or interface index, so this impacts .NET Core functionality.
The text was updated successfully, but these errors were encountered: