Is wssd working accross L2/L3 segments (different IP subnets with multicast routing)

[janwidel]

Hi Team

Simplified diagram:

SERVER_VLAN <- 10.0.5.0/24-> Router <- 10.0.0.1.0/24 -> CLIENT_VLAN

• in SERVERS_VLAN there is VM with Samba + wsdd
• in CLIENT_VLAN there is VM with Windows11
• On router I've IGMPv3 + PIM enabled, and multicast routing enabled for 239.255.255.0/24.

wssd start with below options:
/usr/sbin/wsdd --shortlog --chroot=/run/wsdd -i ens18 -H 64 -v -w HOME

I can see in tcpdump that packets from CLIENT_VLAN(Windows 11) are delivered to SERVER_VLAN (Samba server)

jwidel@fs:~$ tcpdump -i ens18 -l -vv -n host 239.255.255.250

20:04:11.022801 IP (tos 0x0, ttl 3, id 41477, offset 0, flags [none], proto UDP (17), length 165) 10.0.2.120.64081 > 239.255.255.250.1900: [udp sum ok] UDP, length 137

Unfortunately Windows do not discovery Samba server. I can access it via unicast (just typing \fs).
If I move Windows box to the same segment (SERVER_VLAN) discovery is working as expected.

I couldn't find much on info about wsdd in multiple segment scenario. Is it something that is not supported by wsdd (app or protocol itslef)?

EDIT:
It's not wsdd, it's Windows... Running wssd (as host on server-samba) and wsdd (as client -D in client Segment) looks like is WAI.

• Server part of INFO

jwidel@fs:~$ grep INFO server.txt
INFO: using pre-defined UUID cca6c96d-befe-5f5c-8d63-725500b16397
INFO: chrooted successfully to /run/wsdd
INFO: joined multicast group ('239.255.255.250', 3702) on 10.0.5.126%ens18
INFO: scheduling Hello message via ens18 to ('239.255.255.250', 3702)
INFO: 10.0.2.167:43055(ens18) - - "Hello urn:uuid:2bc39450-1455-11ee-b6ce-62599dbae40f UDP" - -
INFO: 10.0.2.167:43055(ens18) - - "Probe urn:uuid:2c5c6dd8-1455-11ee-b6ce-62599dbae40f UDP" - -
INFO: 10.0.2.167:43055(ens18) - - "Resolve urn:uuid:2c5cf0aa-1455-11ee-b6ce-62599dbae40f UDP" - -
INFO: 10.0.2.167 - - "POST /cca6c96d-befe-5f5c-8d63-725500b16397 HTTP/1.1" 200 -

• Client part of INFO:

root@test:~# grep INFO client.txt
2023-06-26 19:10:53,406:wsdd INFO(pid 23971): using pre-defined UUID 4be0643f-1d98-573b-97cd-ca98a65347dd
2023-06-26 19:10:53,407:wsdd INFO(pid 23971): joined multicast group ('239.255.255.250', 3702) on 10.0.2.167%eth0
2023-06-26 19:10:53,407:wsdd INFO(pid 23971): scheduling Hello message via eth0 to ('239.255.255.250', 3702)
2023-06-26 19:10:54,409:wsdd INFO(pid 23971): scheduling Probe message via eth0 to ('239.255.255.250', 3702)
2023-06-26 19:10:54,412:wsdd INFO(pid 23971): 10.0.5.126:3702(eth0) - - "ProbeMatches urn:uuid:2bc3030a-1455-11ee-91a0-2aa01229df58 UDP" - -
2023-06-26 19:10:54,414:wsdd INFO(pid 23971): 10.0.2.120 - - "POST /4be0643f-1d98-573b-97cd-ca98a65347dd HTTP/1.1" 200 -
2023-06-26 19:10:54,414:wsdd INFO(pid 23971): 10.0.5.126:3702(eth0) - - "ResolveMatches urn:uuid:2bc37092-1455-11ee-91a0-2aa01229df58 UDP" - -
2023-06-26 19:10:54,417:wsdd INFO(pid 23971): discovered FS in Workgroup:HOME on 10.0.5.126%eth0
2023-06-26 19:12:38,683:wsdd INFO(pid 23971): received termination/interrupt signal, tearing down
2023-06-26 19:12:38,683:wsdd INFO(pid 23971): shutting down gracefully...
2023-06-26 19:12:38,684:wsdd INFO(pid 23971): scheduling Bye message via eth0 to ('239.255.255.250', 3702)
2023-06-26 19:12:39,416:wsdd INFO(pid 23971): Done.

[janwidel]

Found this: #85

Windows su... ee do not reply if host is in different segment...