Windows 11 disappears for a long time Samba

[qiuzi]

On openwrt run /usr/bin/wsdd2 -i br-lan -N Echo -G WORKGROUP -b vendor:to-be-filled-by-oem-to-be-filled-by-oem,model:To_be_filled_by_O.EM _To_be_filled_by_O.EM
I use windows 11 to start wsdd2 and can find Samba in win11, after 10 minutes refresh File Explorer will disappear! Restarting win11 also fails to discover Samba.
Can only be restored after restarting wsdd2
there is a problem after using this commit

[Doosty]

Same here for windows 10, openwrt samba. Only works for a short time after restarting wsdd2.

[qiuzi]

@Doosty I can use the 2020 source code to use samba normally, and it will not be able to continue to use after 2021

[smaller09]

same here, I have two system runing wsdd2, one is debian 11 on arm, which did not have any problem, another is openwrt nightly on powerpc, that one had same problem as @qiuze mensioned. The icon of openwrt system would disappered after several minutes.
And I google around and found that musl had change time_t to 64 bit. http://musl.libc.org/time64.html. that would be the reason.

[qiuzi]

@smaller09 is there a workable solution?

[smaller09]

I tried to compile my own openwrt with glibc. the problem was still there. So it had nothing with musl. I will try to find out why.

[smaller09]

I open wsdd as a single program use this
/usr/bin/wsdd2 -i br-lan -N OPENWRT -G WORKGROUP -4 -w -W
and when the icon disappear I receive this on console:
wsd_recv: wsd_recv_action: connected_if: No error information

[pesa1234]

OpenWRT 21.02.2 same issue, after some time wsdd2 stop, but process is still present and no log...

[pesa1234]

same here, I have two system runing wsdd2, one is debian 11 on arm, which did not have any problem, another is openwrt nightly on powerpc, that one had same problem as @qiuze mensioned. The icon of openwrt system would disappered after several minutes. And I google around and found that musl had change time_t to 64 bit. http://musl.libc.org/time64.html. that would be the reason.

Hi, if you have a sqm restart or an openvpn restart the problem happen...
This is the message of wsdd2:
wsd_recv: wsd_recv_action: connected_if: No error information

[levshutov]

Done some debugging. It looks like "is_new_addr" function changes global "ifindex" variable to newly bridged interface. It should keep index of bridge itself.
Edit1: It does the same for interfaces not in bridge.

[2K-ZONE]

I just came here while investigating this problem further I have now on an actual OpenWRT Snapshot. Just wondering on how to start some debugging of this.

Previously I used an OpenWRT Snapshot from last year or so with samba+wsdd2 in a docker container: https://github.com/ServerContainers/samba

In this container an ARCH wsdd2 package is delivered, which yields from source point of view to this repository also.
This docker container and its wsdd2 ran for months flawlessly. I wonder, where could be the difference? The container was started in host network mode.

[kimboslice99]

Same issues here

Sure would be nice to see a solution, but an 11 month old thread is disheartening

[Lucky1openwrt]

in file /etc/init.d/wsdd2
line 56
change from
"network_get_device ifname lan"
to
"network_get_device ifname br-lan"

this seems to make it work corectly for me
would love others to test this
maybe it will help track down the fault

[rikka0w0]

This still happens OpenWrt 22.03.5