-
Notifications
You must be signed in to change notification settings - Fork 34
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
Does not work on Windows #118
Comments
Hi @eberkund, are you still experiencing this issue? If so, have you tried doing this the other way around? I'm asking, because I'd like to understand whether this is solely a Windows issue or whether something else in your setup might be causing these issues. If it is solely a Windows issue, it might be worth double checking the interface bindings of the server. To my knowledge, the pion/mdns server tries to bind to all available network interfaces - see: Lines 60 to 65 in 04d95eb
I currently cannot test on Windows, so I cannot confirm this. However, using two Linux machines works. Let me know how it goes. Cheers |
I think this was fixed in bde59ba |
I'll give it a try. Thanks. |
@edaniels, the latest version fixes it. Thanks. |
Great! Thanks for testing :) |
@edaniels I am seeing a regression after updating to v2 |
Ah, sorry! Can you describe the regression so I can look into it? We need windows testing |
I did a basic investigation with WireShark and the client seems to be working fine. I can see the mDNS queries but the server does not respond back. Reverting back to 1.x fixed the issue. |
Gotcha, I likely broke something, sorry! I'll try to test this in the coming days. |
Annoying that it auto closed. @eberkund can you check on v2.0.7? |
It works on 2.0.7, thanks! |
What happened?
I am using Windows (11) and running the example programs does not work. I start the server and run
dns-sd -q my-domain.local
from another computer (macOS) and expect to receive a response from the Windows machine running the pion mDNS server. But I don't get anything. I see the mDNS packets coming through in Wireshark but the Go program does not seem to get them and therefore does not respond.The text was updated successfully, but these errors were encountered: