-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
.NET 9: Zeroconf discovery is broken #110443
Comments
Tagging subscribers to this area: @dotnet/ncl |
Related novotnyllc/Zeroconf#266 |
A change was just made in Zeroconf that fixes the problem: novotnyllc/Zeroconf#266 But I'd like to know what changed in .NET 9 that prompted this. |
Briefly looking at the Zeroconf, I think #89990 is the culprit. We now return more interfaces and some of them may not have IPv4 e.g. trying to fetch that blindly can fail and lead to problems. If anything, it would be interesting to know on what exact interface the app chokes. |
This issue has been marked |
This issue has been automatically marked |
Description
Trying to do a Zeroconf host disccovery results in the following error. This used to work on .NET 8:
NetworkInformationException: The requested protocol has not been configured into the system, or no implementation for it exists.
Reproduction Steps
Expected behavior
The list of available hosts will be returned in a list.
Actual behavior
Resolution fails with the following exception: "NetworkInformationException: The requested protocol has not been configured into the system, or no implementation for it exists."
Regression?
This was working in .NET 8.
Known Workarounds
No response
Configuration
.NET runtime 9.0.0
Windows 10.0.19045
x64
Other information
No response
The text was updated successfully, but these errors were encountered: