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

.NET 9: Zeroconf discovery is broken #110443

Open
pcullen1 opened this issue Dec 5, 2024 · 6 comments
Open

.NET 9: Zeroconf discovery is broken #110443

pcullen1 opened this issue Dec 5, 2024 · 6 comments
Labels
area-System.Net needs-author-action An issue or pull request that requires more info or actions from the author.
Milestone

Comments

@pcullen1
Copy link

pcullen1 commented Dec 5, 2024

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

  1. Install the latest Zeroconf 3.6.11 into a .NET 9 c# app.
  2. Do a discovery, as suggested here: https://github.com/novotnyllc/Zeroconf. Use any protocol

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

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Dec 5, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Dec 5, 2024
@jkotas jkotas added area-System.Net and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Dec 5, 2024
Copy link
Contributor

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

@CarnaViire
Copy link
Member

Related novotnyllc/Zeroconf#266

@pcullen1
Copy link
Author

pcullen1 commented Dec 6, 2024

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.

@CarnaViire
Copy link
Member

#89990 and #101710 seem to touch the area, but I don't have enough insights. Tagging @wfurt for more info

@wfurt
Copy link
Member

wfurt commented Dec 9, 2024

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.

@wfurt wfurt removed the untriaged New issue has not been triaged by the area owner label Dec 9, 2024
@wfurt wfurt added this to the Future milestone Dec 9, 2024
@wfurt wfurt added the needs-author-action An issue or pull request that requires more info or actions from the author. label Dec 9, 2024
Copy link
Contributor

This issue has been marked needs-author-action and may be missing some important information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Net needs-author-action An issue or pull request that requires more info or actions from the author.
Projects
None yet
Development

No branches or pull requests

4 participants