[wsdd2][ 1.8.7.0] WSD/LLMNR Discovery/Name Service Daemon

[outkastm]

About : https://github.com/Netgear/wsdd2

Applicable models: TerraMaster x.64 series - Last version: 1.8.6.0
Applicable models: TerraMaster arm series - Last version: 1.8.7.0
Applicable TOS: 4.1.27 or later versions
App download: https://bit.ly/3RZMbks

Required packages:

Module WebUI for additional settings can be accesses at

http(s)://yournasip:port/modules/wsdd2/www

How to manully install this app on TerraMaster application store?


WSD/LLMNR Discovery/Name Service Daemon

With Microsoft turning off SMB1 feature completely on Windows 10, any Samba shares on the local network become invisible to Windows 10 computers. That's due to the fact that SMB1 is required for Computer Browser service to function.

Newer Windows systems can use WSD (Web Services for Devices) to discover shares hosted on other Windows computers while Linux systems normally utilize mNDS/DNS-SD for service discovery. Microsoft is moving to support mDNS/DNS-SD, but not yet there.

The primary purpose of this project is to enable WSD on Samba servers so that network shares hosted on a Unix box can appear in Windows File Explorer / Network.

NOTE: Make sure there is no firewall rule blocking WSD multicast address 239.255.255.250 and ff02::c, protocol UDP port 3702. Unicast SOAP HTTP WS-Discovery responder listens on TCP port 3702.

LLMNR responder listens on multicast 224.0.0.252 / ff02::1:3 UDP port 5355 and unicast TCP port 5355.

[MisterXY]

Hello, is it possible to build it for the ARM version?
Thx

[marryjanes]

Thank you very much. Please let me know if you can make it for the ARM version

[MisterXY]

you can also install entware and install via opkg wsdd2.

[outkastm]

added arm version (to test)

[alexanderduen]

Thanks for sharing this information about the WSD/LLMNR Discovery/Name Service Daemon! It's great to see a solution for making Samba shares visible to Windows 10 users. For those looking to manually install the app on the TerraMaster application store, you might want to check the compatibility with your specific model and TOS version first.
Also, don't forget to verify your firewall settings to ensure that WSD multicast is not being blocked. This can make a big difference in getting everything up and running smoothly.