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
Multicast SSDP / mDNS discovery is not working anymore since "Local network access" replaced "Advanced networking" #378
Comments
I have this same issue with an OTS android app (Avare) that relies on multicast to receive sensor data. This was working in the last version with Advanced Networking, but not in newer versions with Local Network Access. I would submit that this doesn't seem like it should be a feature request as it was a previously working function that has since been rendered inoperative in version 2307. |
Agreed, it is more a regression than a feature request. |
I can confirm all my mDNS enabled Android apps fail since "Advanced networking" has been replaced by the "Local network access" setting in the "Experimental section". And yes, they all worked fine before, Windows Subsystem for Android is useless to me now. |
Yup and it is still broken on the 2308 update that landed yesterday... |
Same for me. I’m using mDNS domain in VLC for remote access to my NAS. |
Same here. Any app that requires mDNS no longer works as expected version 2306 when the new local network settings were introduced. I also noticed that WSA is causing my home wifi settings in windows to become "public" in windows settings after every reboot since version 2306. I have to manually change it to "private" after each reboot. The two issues may be connected. |
I am on version 2308.40000.4.0 and have found turning local network access "on" actually turns it off. Apps can no longer access local devices. Turning it "off" re-enables local access. |
Still not working in 2309.40000.10.0 :| |
I suppose you meant 2310.40000.0.0. Yes it still not working, which is sad. It worked just fine months ago before "Advanced networking" was replaced by what we have now. |
Hello, |
Did anyone test if it's been fixed in WSA 2311.40000.1.0 ? |
I gave up on Windows subsystem for Android. It's a fiasco. |
Sadly, it doesn't. WSA hates multicast, UDP and SSDP. You have to wonder if it worked previously by pure luck. Again and again, it makes a whole category of apps entirely unusable. |
Any news about this? I would love to use the advanced Vulkan driver for newer versions. But I need local network to be working too. For now, I am downgrading to v2305.. Sad. I am using CIFS Document Provider, in v2305, it detects the NAS server IP address and other local network devices IP addresses fine. But anything above v2306+ fails as mentioned in the original post above. |
With "Developer mode" enabled in WSA settings there is a possibility to run in Windows Terminal With "Local network access" disabled command With "Local network access" enabled command It is just a guess. |
How were you able to downgrade to 2305? At this point I'm willing to remove myself from windows updates entirely if I can find a way to downgrade WSA to 2305. |
@johnbasol Download the package manually from WSABuilds repo here Specifically, page 5 of releases from June 22 more than likely you need the x64 build unless you have Arm64 CPU. |
Having a similar issue , but found that with 2306 . if i start the app with the wifi off on and then turn it on after the app starts it seems to work . Still testing but seems to be connecting for now . |
@RebelliousX, you are right ! any one if interested and facing this error do uninstall current wsa and install this one : https://github.com/MustardChef/WSABuilds/releases/tag/Windows_11_2305.40000.6.0 it has advance network settings options and works as expected... |
Thank's a lot . With this Build I'm able to control my Primare Audioplayer from my Laptop . |
Steps to reproduce
I'm the developer of an app called BubbleUPnP, available on the Amazon appstore, whose purpose is to play to networked streamers (Chromecast, UPnP/DLNA, ...) media that can be stored on UPnP/DLNA media servers running on various machines (NAS, PC, mac, ...) on the local network.
When the "Advanced networking" option existed and was enabled, the app could detect these networked devices fine using the SSDP and mDNS protocols, both using multicast UDP under the hood.
Since "Advanced networking" has been replaced by the "Local network access" setting in the "Experimental section", this discovery does not work anymore (with or without "Local network access" enabled"), making my app almost useless while it worked before. This is a severe regression.
To reproduce it:
If you did the same with an older version of WSA (before v2306) and with "Advanced networking" enabled, these devices would be detected
✔️ Expected Behavior
With "Local network access" setting enabled, SSDP and mDNS multicast discovery should work to detect on the local network devices using these protocols.
❌ Actual Behavior
With "Local network access" setting enabled, SSDP and mDNS multicast discovery does not work while it did with the older "Advanced networking" enabled.
Other Software
No response
Please specify the version of Windows Subsystem for Android
2307.40000.2.0
The text was updated successfully, but these errors were encountered: