-
Notifications
You must be signed in to change notification settings - Fork 822
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
.local names can only be resolved from wsl2 connected via Ethernet but not via WiFi #5944
Comments
Just came across the same issue when trying to connect to my raspberry pi. Installed
|
So now it sometimes works via WiFi here as well. However I cannot say yet when it happens and when it doesn't happen. The only thing I can say is that I installed wireshark and it looked like the mDNS request went out but no response came back while a request from the Windows system directly (launching ping via cmd/powershell) would be properly answered by the other host. |
I can't get it to work even on ethernet either. Same setup. At daemon startup, this occurs:
and apparently the original maps to the host Windows machine, which I can confirm by resolving to it from another machine on the local network (or from WSL for that matter). Unanswered query (from WSL):
Answered Windows host IP resolution (from WSL):
I have confirmed with WireShark on the host machine, that the MDNS requests don't get "mirrored / bridged" from the vEthernet (WSL) virtual bridge adapter, to the physical Ethernet adapter the same way they get bridged for normal packets. Probably because the bridge network is a valid subnet, and there's no implicit reason to forward a multicast packet to another (gateway) network. Even though that is undesirable in this case. |
Update: As long as MDNS support is enabled on the Windows host (which apparently it is) then trying to resolve a
prompts the host to issue an MDNS request and forward the reply as a DNS reply to the WSL DNS request. It works automagically. |
I am having a similar issue. I can resolve the MDNS from Windows From Windows
From Ubuntu on WSL2 (with and without
|
Retracting my comment above about 'inconsistent behavior' - this is not specific to Ubuntu/WSL2 on my network and may be due to the version of However, my notes above confirm the behavior noted by vjancik - that closing |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Environment
Steps to reproduce
Install Ubuntu on WSL2 and maybe install avahi-daemon as well. It's not required to start dbus and/or avahi-daemon. Connect you laptop via Ethernet to a network with other hosts that can be resolved using mDNS. Then just run
ping abc.local
in Ubuntu and it should just work fine. However when you disconnect the Ethernet cable and connect your host to the network via WiFi, then the ping command doesn't work anymore.I then booted into Linux natively on the same machine and there I was able to resolve the host via Ethernet and via WiFi, so it's not a problem of the local WiFi router.
Expected behavior
I think .local names should resolve just fine.
Actual behavior
Resolving .local names from Ubuntu doesn't work when the host system is connected via WiFi instead of Ethernet.
Related issues
It sounds like #384 and #3365 are related but they are already closed.
The text was updated successfully, but these errors were encountered: