search

christgau / wsdd

A Web Service Discovery host daemon.
MIT License
861 stars 101 forks source link

Samba share not showing in Win 10 VM guest #177

Closed FlexMcMurphy closed 1 year ago

FlexMcMurphy commented 1 year ago

Hello,

I have a Pi on my LAN with a few Samba shares. I successfully use wsdd to make that Pi auto-populate in the Network Neighbourhood of a Win 10 bare metal install.

However I set up Win 10 also in a VM in Virtualbox and in this case that Pi does not auto-populate. I can "Map network drive" to that Pi, ping it also and access the shares that way but wondering why does that Pi not auto-populate?

Confusingly I have two other devices that also use wsdd and they DO auto-populate in that Win 10 VM.

I tried restarting that Pi. I checked its smb.conf. I am using SMBv3 which Win 10 supports.

The Virtualbox Network Settings of the Win 10 VM are set to "Bridged Adapter" and point to the correct Wifi adapter so I have network connectivity from the Win 10 guest to the lan and can ping the Pi. After some more research I think my issue might be related to this issue and I need to specify the interface that is connected to the network on which the host should be announced using the -i/--interface option as mentioned in the WSDD GitHub Readme, but I might be wrong and am confused about how to do that?!

Update

Ok I am trying to debug... I now manually start wsdd on the Pi like this: sudo /usr/bin/wsdd -vv -i eth0

eth0 is the interface on the Pi that it is connected to the router with. I restarted the Win 10 VM and some messages comes through to wsdd... see below. Also in the output below you can see me successfully connecting to the Pi from other operating systems (different ip addresses, e.g: 192.168.1.233) Ipv6 address below fe80::5801:cc50:46af:57c7 (ipv4=192.168.1.187) is the ip address of the Win 10 VM in Virtualbox, and the output shows responses like "known message" and "dropping it". Why is this?

ubuntu@ubuntu:/etc/systemd/system$ sudo /usr/bin/wsdd -vv -i eth0
/usr/bin/wsdd:1832: DeprecationWarning: There is no current event loop
  asyncio.get_event_loop().set_debug(True)
2023-05-21 11:58:35,922:wsdd INFO(pid 2268): using pre-defined UUID 724fc160-2b2e-597e-b9ed-7f65313cd73f
2023-05-21 11:58:35,923:asyncio DEBUG(pid 2268): Using selector: EpollSelector
2023-05-21 11:58:35,925:wsdd DEBUG(pid 2268): netlink message with 164 bytes
2023-05-21 11:58:35,925:wsdd DEBUG(pid 2268): RTM new/del addr family: 2 flags: 128 scope: 254 idx: 1
2023-05-21 11:58:35,926:wsdd DEBUG(pid 2268): rt_attr 8 1
2023-05-21 11:58:35,926:wsdd DEBUG(pid 2268): rt_attr 8 2
2023-05-21 11:58:35,926:wsdd DEBUG(pid 2268): rt_attr 7 3
2023-05-21 11:58:35,926:wsdd DEBUG(pid 2268): rt_attr 8 8
2023-05-21 11:58:35,926:wsdd DEBUG(pid 2268): rt_attr 20 6
2023-05-21 11:58:35,926:wsdd DEBUG(pid 2268): new address 127.0.0.1%lo
2023-05-21 11:58:35,926:wsdd DEBUG(pid 2268): ignoring that address on lo
2023-05-21 11:58:35,927:wsdd DEBUG(pid 2268): RTM new/del addr family: 2 flags: 128 scope: 0 idx: 2
2023-05-21 11:58:35,927:wsdd DEBUG(pid 2268): rt_attr 8 1
2023-05-21 11:58:35,927:wsdd DEBUG(pid 2268): rt_attr 8 2
2023-05-21 11:58:35,927:wsdd DEBUG(pid 2268): rt_attr 8 4
2023-05-21 11:58:35,927:wsdd DEBUG(pid 2268): rt_attr 9 3
2023-05-21 11:58:35,927:wsdd DEBUG(pid 2268): rt_attr 8 8
2023-05-21 11:58:35,927:wsdd DEBUG(pid 2268): rt_attr 20 6
2023-05-21 11:58:35,927:wsdd DEBUG(pid 2268): new address 192.168.1.34%eth0
2023-05-21 11:58:35,927:wsdd DEBUG(pid 2268): handling traffic for 192.168.1.34%eth0
2023-05-21 11:58:35,928:wsdd INFO(pid 2268): joined multicast group 239.255.255.250 on 192.168.1.34%eth0
2023-05-21 11:58:35,928:wsdd DEBUG(pid 2268): transport address on eth0 is 192.168.1.34
2023-05-21 11:58:35,928:wsdd DEBUG(pid 2268): will listen for HTTP traffic on address ('192.168.1.34', 5357)
2023-05-21 11:58:35,930:wsdd DEBUG(pid 2268): constructed xml for WSD message: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/10" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07"><soap:Header><wsa:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Hello</wsa:Action><wsa:MessageID>urn:uuid:6f2f109e-f7c6-11ed-902c-b9066e9f0bf3</wsa:MessageID><wsd:AppSequence InstanceId="1684666715" SequenceId="urn:uuid:6f2f109f-f7c6-11ed-902c-b9066e9f0bf3" MessageNumber="0" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://192.168.1.34:5357/724fc160-2b2e-597e-b9ed-7f65313cd73f</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2023-05-21 11:58:35,930:wsdd INFO(pid 2268): scheduling Hello message via eth0 to 239.255.255.250%eth0
2023-05-21 11:58:35,960:wsdd DEBUG(pid 2268): netlink message with 144 bytes
2023-05-21 11:58:35,961:wsdd DEBUG(pid 2268): RTM new/del addr family: 10 flags: 128 scope: 254 idx: 1
2023-05-21 11:58:35,961:wsdd DEBUG(pid 2268): rt_attr 20 1
2023-05-21 11:58:35,961:wsdd DEBUG(pid 2268): rt_attr 20 6
2023-05-21 11:58:35,962:wsdd DEBUG(pid 2268): rt_attr 8 8
2023-05-21 11:58:35,962:wsdd DEBUG(pid 2268): new address ::1%lo
2023-05-21 11:58:35,962:wsdd DEBUG(pid 2268): ignoring that address on lo
2023-05-21 11:58:35,963:wsdd DEBUG(pid 2268): RTM new/del addr family: 10 flags: 128 scope: 253 idx: 2
2023-05-21 11:58:35,963:wsdd DEBUG(pid 2268): rt_attr 20 1
2023-05-21 11:58:35,963:wsdd DEBUG(pid 2268): rt_attr 20 6
2023-05-21 11:58:35,963:wsdd DEBUG(pid 2268): rt_attr 8 8
2023-05-21 11:58:35,964:wsdd DEBUG(pid 2268): new address fe80::dea6:32ff:fe26:66cf%eth0
2023-05-21 11:58:35,964:wsdd DEBUG(pid 2268): handling traffic for fe80::dea6:32ff:fe26:66cf%eth0
2023-05-21 11:58:35,965:wsdd INFO(pid 2268): joined multicast group [ff02::c] on fe80::dea6:32ff:fe26:66cf%eth0
2023-05-21 11:58:35,965:wsdd DEBUG(pid 2268): transport address on eth0 is [fe80::dea6:32ff:fe26:66cf]
2023-05-21 11:58:35,965:wsdd DEBUG(pid 2268): will listen for HTTP traffic on address ('fe80::dea6:32ff:fe26:66cf', 5357, 0, 2)
2023-05-21 11:58:35,968:wsdd DEBUG(pid 2268): constructed xml for WSD message: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/10" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07"><soap:Header><wsa:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Hello</wsa:Action><wsa:MessageID>urn:uuid:6f2f10a0-f7c6-11ed-902c-b9066e9f0bf3</wsa:MessageID><wsd:AppSequence InstanceId="1684666715" SequenceId="urn:uuid:6f2f10a1-f7c6-11ed-902c-b9066e9f0bf3" MessageNumber="1" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://[fe80::dea6:32ff:fe26:66cf]:5357/724fc160-2b2e-597e-b9ed-7f65313cd73f</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2023-05-21 11:58:35,968:wsdd INFO(pid 2268): scheduling Hello message via eth0 to ff02::c%eth0
2023-05-21 11:58:35,971:wsdd DEBUG(pid 2268): netlink message with 20 bytes
2023-05-21 11:58:35,972:wsdd DEBUG(pid 2268): invalid rtm_message type 3
2023-05-21 12:00:11,933:wsdd INFO(pid 2268): [fe80::5801:cc50:46af:57c7]:61017(eth0) - - "Probe urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801 UDP" - -
2023-05-21 12:00:11,934:wsdd DEBUG(pid 2268): incoming message content is <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof"><soap:Header><wsa:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Probe</wsa:Action><wsa:MessageID>urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801</wsa:MessageID></soap:Header><soap:Body><wsd:Probe><wsd:Types>wsdp:Device</wsd:Types></wsd:Probe></soap:Body></soap:Envelope>
2023-05-21 12:00:11,937:wsdd DEBUG(pid 2268): constructed xml for WSD message: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/10" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07"><soap:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</wsa:Action><wsa:MessageID>urn:uuid:a8687a44-f7c6-11ed-902c-b9066e9f0bf3</wsa:MessageID><wsa:RelatesTo>urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801</wsa:RelatesTo><wsd:AppSequence InstanceId="1684666715" SequenceId="urn:uuid:a8687a45-f7c6-11ed-902c-b9066e9f0bf3" MessageNumber="2" /></soap:Header><soap:Body><wsd:ProbeMatches><wsd:ProbeMatch><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference><wsd:Types>wsdp:Device pub:Computer</wsd:Types><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:ProbeMatch></wsd:ProbeMatches></soap:Body></soap:Envelope>
2023-05-21 12:00:11,954:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:12,165:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:12,199:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:12,634:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:12,678:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:13,540:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:13,638:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:15,384:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:15,558:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:17,367:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:17,570:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:19,371:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:00:19,571:wsdd DEBUG(pid 2268): known message (urn:uuid:773bc85d-18d1-4aba-b37d-27ac95026801): dropping it
2023-05-21 12:01:54,482:wsdd INFO(pid 2268): 192.168.1.233:3702(eth0) - - "Probe urn:uuid:f4c2e673-e582-49ee-aed5-c4ee133a7779 UDP" - -
2023-05-21 12:01:54,482:wsdd DEBUG(pid 2268): incoming message content is <?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:soap-enc="http://www.w3.org/2003/05/soap-encoding" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:n1="http://schemas.xmlsoap.org/ws/2005/04/discovery"><soap:Header><wsa:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To><wsa:ReplyTo><wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address></wsa:ReplyTo><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Probe</wsa:Action><wsa:MessageID>urn:uuid:f4c2e673-e582-49ee-aed5-c4ee133a7779</wsa:MessageID></soap:Header><soap:Body><n1:Probe><n1:Types xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof">wsdp:Device</n1:Types></n1:Probe></soap:Body></soap:Envelope>

2023-05-21 12:01:54,485:wsdd DEBUG(pid 2268): constructed xml for WSD message: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/10" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07"><soap:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</wsa:Action><wsa:MessageID>urn:uuid:e5880f34-f7c6-11ed-902c-b9066e9f0bf3</wsa:MessageID><wsa:RelatesTo>urn:uuid:f4c2e673-e582-49ee-aed5-c4ee133a7779</wsa:RelatesTo><wsd:AppSequence InstanceId="1684666715" SequenceId="urn:uuid:e5880f35-f7c6-11ed-902c-b9066e9f0bf3" MessageNumber="3" /></soap:Header><soap:Body><wsd:ProbeMatches><wsd:ProbeMatch><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference><wsd:Types>wsdp:Device pub:Computer</wsd:Types><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:ProbeMatch></wsd:ProbeMatches></soap:Body></soap:Envelope>
2023-05-21 12:01:54,487:wsdd DEBUG(pid 2268): known message (urn:uuid:f4c2e673-e582-49ee-aed5-c4ee133a7779): dropping it
2023-05-21 12:01:54,784:wsdd INFO(pid 2268): 192.168.1.233:37974(eth0) - - "Resolve urn:uuid:377c7a2d-f533-4660-b285-775f725d8745 UDP" - -
2023-05-21 12:01:54,784:wsdd DEBUG(pid 2268): incoming message content is <?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:soap-enc="http://www.w3.org/2003/05/soap-encoding" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:n1="http://schemas.xmlsoap.org/ws/2005/04/discovery"><soap:Header><wsa:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To><wsa:ReplyTo><wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address></wsa:ReplyTo><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Resolve</wsa:Action><wsa:MessageID>urn:uuid:377c7a2d-f533-4660-b285-775f725d8745</wsa:MessageID></soap:Header><soap:Body><n1:Resolve><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference></n1:Resolve></soap:Body></soap:Envelope>

2023-05-21 12:01:54,786:wsdd DEBUG(pid 2268): constructed xml for WSD message: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/10" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07"><soap:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/ResolveMatches</wsa:Action><wsa:MessageID>urn:uuid:e5880f36-f7c6-11ed-902c-b9066e9f0bf3</wsa:MessageID><wsa:RelatesTo>urn:uuid:377c7a2d-f533-4660-b285-775f725d8745</wsa:RelatesTo><wsd:AppSequence InstanceId="1684666715" SequenceId="urn:uuid:e5880f37-f7c6-11ed-902c-b9066e9f0bf3" MessageNumber="4" /></soap:Header><soap:Body><wsd:ResolveMatches><wsd:ResolveMatch><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference><wsd:Types>wsdp:Device pub:Computer</wsd:Types><wsd:XAddrs>http://192.168.1.34:5357/724fc160-2b2e-597e-b9ed-7f65313cd73f</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:ResolveMatch></wsd:ResolveMatches></soap:Body></soap:Envelope>
2023-05-21 12:01:54,791:wsdd DEBUG(pid 2268): known message (urn:uuid:377c7a2d-f533-4660-b285-775f725d8745): dropping it
2023-05-21 12:01:54,933:wsdd DEBUG(pid 2268): processing WSD Get message (urn:uuid:ccc41314-a0a3-45ee-a80d-e8577c9c124e)
2023-05-21 12:01:54,934:wsdd DEBUG(pid 2268): incoming message content is b'<?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:soap-enc="http://www.w3.org/2003/05/soap-encoding" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:n1="http://schemas.xmlsoap.org/ws/2004/09/transfer"><soap:Header><wsa:To>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:To><wsa:From><wsa:Address>urn:uuid:9fd92b47-bdd3-4504-bd76-4bcc920fd949</wsa:Address></wsa:From><wsa:ReplyTo><wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address></wsa:ReplyTo><wsa:Action>http://schemas.xmlsoap.org/ws/2004/09/transfer/Get</wsa:Action><wsa:MessageID>urn:uuid:ccc41314-a0a3-45ee-a80d-e8577c9c124e</wsa:MessageID></soap:Header><soap:Body/></soap:Envelope>\n'
2023-05-21 12:01:54,936:wsdd DEBUG(pid 2268): constructed xml for WSD message: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/10" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07"><soap:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2004/09/transfer/GetResponse</wsa:Action><wsa:MessageID>urn:uuid:e5880f38-f7c6-11ed-902c-b9066e9f0bf3</wsa:MessageID><wsa:RelatesTo>urn:uuid:ccc41314-a0a3-45ee-a80d-e8577c9c124e</wsa:RelatesTo></soap:Header><soap:Body><wsx:Metadata><wsx:MetadataSection Dialect="http://schemas.xmlsoap.org/ws/2006/02/devprof/ThisDevice"><wsdp:ThisDevice><wsdp:FriendlyName>WSD Device ubuntu</wsdp:FriendlyName><wsdp:FirmwareVersion>1.0</wsdp:FirmwareVersion><wsdp:SerialNumber>1</wsdp:SerialNumber></wsdp:ThisDevice></wsx:MetadataSection><wsx:MetadataSection Dialect="http://schemas.xmlsoap.org/ws/2006/02/devprof/ThisModel"><wsdp:ThisModel><wsdp:Manufacturer>wsdd</wsdp:Manufacturer><wsdp:ModelName>wsdd</wsdp:ModelName><pnpx:DeviceCategory>Computers</pnpx:DeviceCategory></wsdp:ThisModel></wsx:MetadataSection><wsx:MetadataSection Dialect="http://schemas.xmlsoap.org/ws/2006/02/devprof/Relationship"><wsdp:Relationship Type="http://schemas.xmlsoap.org/ws/2006/02/devprof/host"><wsdp:Host><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference><wsdp:Types>pub:Computer</wsdp:Types><wsdp:ServiceId>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsdp:ServiceId><pub:Computer>UBUNTU/Workgroup:WORKGROUP</pub:Computer></wsdp:Host></wsdp:Relationship></wsx:MetadataSection></wsx:Metadata></soap:Body></soap:Envelope>
2023-05-21 12:01:54,937:wsdd INFO(pid 2268): 192.168.1.233 - - "POST /724fc160-2b2e-597e-b9ed-7f65313cd73f HTTP/1.1" 200 -

..
...
....

To clarify... I have two other devices running wsdd and they both get populated fine in the Win 10 VM. These versions of wsdd appear to be written in C. Whereas the wsdd I have on the Pi is the christgau python3 version. As per the christgau wsdd Issue 8 there is something different about how these different versions handle multicast UDP messages and scenarios with network interfaces on virtualized bridges. Or such is my meagre understanding of all this!

Should I be making the Win 10 VM talk on the network over ipv4 and not ipv6 maybe?

Any help much appreciated.

Cheers,

Flex

FlexMcMurphy commented 1 year ago

Hello,

I have done some more tests.

First of all, I am sorry to say but after reading through Issue 8 I tried installing wsdd2.

# sudo apt update
# sudo apt install wsdd2

Now it DOES work... my Pi auto-populates in the Network Neighbourhood of the Win 10 VM. That satisfied me for about 2 hrs because now I'm really curious what exactly is going wrong with the Python3 version of wsdd?

I see from issue 15 that someone else found they had to specify ipv4 or else it would not work. I was wondering earlier if that might be related. So I tried that with wsdd and it DOES work that way.

I ran the command as below and then opened up the file explorer in the Win 10 VM. The Pi machine was already there.

ubuntu@ubuntu:~$ sudo /usr/bin/wsdd -vv -i eth0 -4
/usr/bin/wsdd:1832: DeprecationWarning: There is no current event loop
  asyncio.get_event_loop().set_debug(True)
2023-05-21 21:22:43,237:wsdd INFO(pid 6182): using pre-defined UUID 724fc160-2b2e-597e-b9ed-7f65313cd73f
2023-05-21 21:22:43,238:asyncio DEBUG(pid 6182): Using selector: EpollSelector
2023-05-21 21:22:43,240:wsdd DEBUG(pid 6182): netlink message with 164 bytes
2023-05-21 21:22:43,241:wsdd DEBUG(pid 6182): RTM new/del addr family: 2 flags: 128 scope: 254 idx: 1
2023-05-21 21:22:43,241:wsdd DEBUG(pid 6182): rt_attr 8 1
2023-05-21 21:22:43,241:wsdd DEBUG(pid 6182): rt_attr 8 2
2023-05-21 21:22:43,241:wsdd DEBUG(pid 6182): rt_attr 7 3
2023-05-21 21:22:43,241:wsdd DEBUG(pid 6182): rt_attr 8 8
2023-05-21 21:22:43,241:wsdd DEBUG(pid 6182): rt_attr 20 6
2023-05-21 21:22:43,241:wsdd DEBUG(pid 6182): new address 127.0.0.1%lo
2023-05-21 21:22:43,241:wsdd DEBUG(pid 6182): ignoring that address on lo
2023-05-21 21:22:43,242:wsdd DEBUG(pid 6182): RTM new/del addr family: 2 flags: 128 scope: 0 idx: 2
2023-05-21 21:22:43,242:wsdd DEBUG(pid 6182): rt_attr 8 1
2023-05-21 21:22:43,242:wsdd DEBUG(pid 6182): rt_attr 8 2
2023-05-21 21:22:43,242:wsdd DEBUG(pid 6182): rt_attr 8 4
2023-05-21 21:22:43,242:wsdd DEBUG(pid 6182): rt_attr 9 3
2023-05-21 21:22:43,242:wsdd DEBUG(pid 6182): rt_attr 8 8
2023-05-21 21:22:43,242:wsdd DEBUG(pid 6182): rt_attr 20 6
2023-05-21 21:22:43,242:wsdd DEBUG(pid 6182): new address 192.168.1.34%eth0
2023-05-21 21:22:43,243:wsdd DEBUG(pid 6182): handling traffic for 192.168.1.34%eth0
2023-05-21 21:22:43,243:wsdd INFO(pid 6182): joined multicast group 239.255.255.250 on 192.168.1.34%eth0
2023-05-21 21:22:43,243:wsdd DEBUG(pid 6182): transport address on eth0 is 192.168.1.34
2023-05-21 21:22:43,243:wsdd DEBUG(pid 6182): will listen for HTTP traffic on address ('192.168.1.34', 5357)
2023-05-21 21:22:43,245:wsdd DEBUG(pid 6182): constructed xml for WSD message: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/10" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07"><soap:Header><wsa:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Hello</wsa:Action><wsa:MessageID>urn:uuid:3dc17458-f815-11ed-902c-b9066e9f0bf3</wsa:MessageID><wsd:AppSequence InstanceId="1684700563" SequenceId="urn:uuid:3dc17459-f815-11ed-902c-b9066e9f0bf3" MessageNumber="0" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://192.168.1.34:5357/724fc160-2b2e-597e-b9ed-7f65313cd73f</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2023-05-21 21:22:43,245:wsdd INFO(pid 6182): scheduling Hello message via eth0 to 239.255.255.250%eth0
2023-05-21 21:22:43,274:wsdd DEBUG(pid 6182): netlink message with 144 bytes
2023-05-21 21:22:43,275:wsdd DEBUG(pid 6182): RTM new/del addr family: 10 flags: 128 scope: 254 idx: 1
2023-05-21 21:22:43,275:wsdd DEBUG(pid 6182): rt_attr 20 1
2023-05-21 21:22:43,275:wsdd DEBUG(pid 6182): rt_attr 20 6
2023-05-21 21:22:43,276:wsdd DEBUG(pid 6182): rt_attr 8 8
2023-05-21 21:22:43,276:wsdd DEBUG(pid 6182): new address ::1%lo
2023-05-21 21:22:43,276:wsdd DEBUG(pid 6182): ignoring that address on lo
2023-05-21 21:22:43,276:wsdd DEBUG(pid 6182): RTM new/del addr family: 10 flags: 128 scope: 253 idx: 2
2023-05-21 21:22:43,277:wsdd DEBUG(pid 6182): rt_attr 20 1
2023-05-21 21:22:43,277:wsdd DEBUG(pid 6182): rt_attr 20 6
2023-05-21 21:22:43,277:wsdd DEBUG(pid 6182): rt_attr 8 8
2023-05-21 21:22:43,277:wsdd DEBUG(pid 6182): new address fe80::dea6:32ff:fe26:66cf%eth0
2023-05-21 21:22:43,277:wsdd DEBUG(pid 6182): ignoring that address on eth0
2023-05-21 21:22:43,278:wsdd DEBUG(pid 6182): netlink message with 20 bytes
2023-05-21 21:22:43,278:wsdd DEBUG(pid 6182): invalid rtm_message type 3
2023-05-21 21:23:27,887:wsdd INFO(pid 6182): 192.168.1.187:59212(eth0) - - "Probe urn:uuid:4d6edace-b1e6-4d71-a0ea-c7176e73ee0e UDP" - -
2023-05-21 21:23:27,887:wsdd DEBUG(pid 6182): incoming message content is <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof"><soap:Header><wsa:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Probe</wsa:Action><wsa:MessageID>urn:uuid:4d6edace-b1e6-4d71-a0ea-c7176e73ee0e</wsa:MessageID></soap:Header><soap:Body><wsd:Probe><wsd:Types>wsdp:Device</wsd:Types></wsd:Probe></soap:Body></soap:Envelope>
2023-05-21 21:23:27,891:wsdd DEBUG(pid 6182): constructed xml for WSD message: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/10" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07"><soap:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</wsa:Action><wsa:MessageID>urn:uuid:585dc596-f815-11ed-902c-b9066e9f0bf3</wsa:MessageID><wsa:RelatesTo>urn:uuid:4d6edace-b1e6-4d71-a0ea-c7176e73ee0e</wsa:RelatesTo><wsd:AppSequence InstanceId="1684700563" SequenceId="urn:uuid:585dc597-f815-11ed-902c-b9066e9f0bf3" MessageNumber="1" /></soap:Header><soap:Body><wsd:ProbeMatches><wsd:ProbeMatch><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference><wsd:Types>wsdp:Device pub:Computer</wsd:Types><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:ProbeMatch></wsd:ProbeMatches></soap:Body></soap:Envelope>
2023-05-21 21:23:27,975:wsdd INFO(pid 6182): 192.168.1.187:52416(eth0) - - "Resolve urn:uuid:a053fea3-a37a-4dc9-86d8-b666fa217df2 UDP" - -
2023-05-21 21:23:27,976:wsdd DEBUG(pid 6182): incoming message content is <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery"><soap:Header><wsa:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Resolve</wsa:Action><wsa:MessageID>urn:uuid:a053fea3-a37a-4dc9-86d8-b666fa217df2</wsa:MessageID></soap:Header><soap:Body><wsd:Resolve><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference></wsd:Resolve></soap:Body></soap:Envelope>
2023-05-21 21:23:27,978:wsdd DEBUG(pid 6182): constructed xml for WSD message: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/10" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07"><soap:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/ResolveMatches</wsa:Action><wsa:MessageID>urn:uuid:585dc598-f815-11ed-902c-b9066e9f0bf3</wsa:MessageID><wsa:RelatesTo>urn:uuid:a053fea3-a37a-4dc9-86d8-b666fa217df2</wsa:RelatesTo><wsd:AppSequence InstanceId="1684700563" SequenceId="urn:uuid:585dc599-f815-11ed-902c-b9066e9f0bf3" MessageNumber="2" /></soap:Header><soap:Body><wsd:ResolveMatches><wsd:ResolveMatch><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference><wsd:Types>wsdp:Device pub:Computer</wsd:Types><wsd:XAddrs>http://192.168.1.34:5357/724fc160-2b2e-597e-b9ed-7f65313cd73f</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:ResolveMatch></wsd:ResolveMatches></soap:Body></soap:Envelope>
2023-05-21 21:23:27,996:wsdd DEBUG(pid 6182): processing WSD Get message (urn:uuid:6cc3a49f-2869-4acd-82a4-853b9168bf40)
2023-05-21 21:23:27,997:wsdd DEBUG(pid 6182): incoming message content is b'<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:lms="http://schemas.microsoft.com/windows/lms/2007/08"><soap:Header><wsa:To>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2004/09/transfer/Get</wsa:Action><wsa:MessageID>urn:uuid:6cc3a49f-2869-4acd-82a4-853b9168bf40</wsa:MessageID><wsa:ReplyTo><wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address></wsa:ReplyTo><wsa:From><wsa:Address>urn:uuid:d3d17e8b-40bb-476f-84ea-8849a57a3dd6</wsa:Address></wsa:From><lms:LargeMetadataSupport/></soap:Header><soap:Body/></soap:Envelope>'
2023-05-21 21:23:27,998:wsdd DEBUG(pid 6182): constructed xml for WSD message: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/10" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07"><soap:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2004/09/transfer/GetResponse</wsa:Action><wsa:MessageID>urn:uuid:585dc59a-f815-11ed-902c-b9066e9f0bf3</wsa:MessageID><wsa:RelatesTo>urn:uuid:6cc3a49f-2869-4acd-82a4-853b9168bf40</wsa:RelatesTo></soap:Header><soap:Body><wsx:Metadata><wsx:MetadataSection Dialect="http://schemas.xmlsoap.org/ws/2006/02/devprof/ThisDevice"><wsdp:ThisDevice><wsdp:FriendlyName>WSD Device ubuntu</wsdp:FriendlyName><wsdp:FirmwareVersion>1.0</wsdp:FirmwareVersion><wsdp:SerialNumber>1</wsdp:SerialNumber></wsdp:ThisDevice></wsx:MetadataSection><wsx:MetadataSection Dialect="http://schemas.xmlsoap.org/ws/2006/02/devprof/ThisModel"><wsdp:ThisModel><wsdp:Manufacturer>wsdd</wsdp:Manufacturer><wsdp:ModelName>wsdd</wsdp:ModelName><pnpx:DeviceCategory>Computers</pnpx:DeviceCategory></wsdp:ThisModel></wsx:MetadataSection><wsx:MetadataSection Dialect="http://schemas.xmlsoap.org/ws/2006/02/devprof/Relationship"><wsdp:Relationship Type="http://schemas.xmlsoap.org/ws/2006/02/devprof/host"><wsdp:Host><wsa:EndpointReference><wsa:Address>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsa:Address></wsa:EndpointReference><wsdp:Types>pub:Computer</wsdp:Types><wsdp:ServiceId>urn:uuid:724fc160-2b2e-597e-b9ed-7f65313cd73f</wsdp:ServiceId><pub:Computer>UBUNTU/Workgroup:WORKGROUP</pub:Computer></wsdp:Host></wsdp:Relationship></wsx:MetadataSection></wsx:Metadata></soap:Body></soap:Envelope>
2023-05-21 21:23:27,999:wsdd INFO(pid 6182): 192.168.1.187 - - "POST /724fc160-2b2e-597e-b9ed-7f65313cd73f HTTP/1.1" 200 -
2023-05-21 21:23:28,136:wsdd DEBUG(pid 6182): known message (urn:uuid:4d6edace-b1e6-4d71-a0ea-c7176e73ee0e): dropping it
2023-05-21 21:23:28,162:wsdd DEBUG(pid 6182): known message (urn:uuid:a053fea3-a37a-4dc9-86d8-b666fa217df2): dropping it
2023-05-21 21:23:28,538:wsdd DEBUG(pid 6182): known message (urn:uuid:a053fea3-a37a-4dc9-86d8-b666fa217df2): dropping it
2023-05-21 21:23:28,636:wsdd DEBUG(pid 6182): known message (urn:uuid:4d6edace-b1e6-4d71-a0ea-c7176e73ee0e): dropping it
2023-05-21 21:23:29,305:wsdd DEBUG(pid 6182): known message (urn:uuid:a053fea3-a37a-4dc9-86d8-b666fa217df2): dropping it
2023-05-21 21:23:29,584:wsdd DEBUG(pid 6182): known message (urn:uuid:4d6edace-b1e6-4d71-a0ea-c7176e73ee0e): dropping it
2023-05-21 21:23:30,812:wsdd DEBUG(pid 6182): known message (urn:uuid:a053fea3-a37a-4dc9-86d8-b666fa217df2): dropping it
2023-05-21 21:23:31,509:wsdd DEBUG(pid 6182): known message (urn:uuid:4d6edace-b1e6-4d71-a0ea-c7176e73ee0e): dropping it
2023-05-21 21:23:32,836:wsdd DEBUG(pid 6182): known message (urn:uuid:a053fea3-a37a-4dc9-86d8-b666fa217df2): dropping it
2023-05-21 21:23:33,525:wsdd DEBUG(pid 6182): known message (urn:uuid:4d6edace-b1e6-4d71-a0ea-c7176e73ee0e): dropping it
2023-05-21 21:23:34,852:wsdd DEBUG(pid 6182): known message (urn:uuid:a053fea3-a37a-4dc9-86d8-b666fa217df2): dropping it
2023-05-21 21:23:35,525:wsdd DEBUG(pid 6182): known message (urn:uuid:4d6edace-b1e6-4d71-a0ea-c7176e73ee0e): dropping it
2023-05-21 21:25:01,656:wsdd INFO(pid 6182): 192.168.1.187:62179(eth0) - - "Hello urn:uuid:4d27bca3-95bf-4341-a51d-51dced508722 UDP" - -
2023-05-21 21:25:01,656:wsdd DEBUG(pid 6182): incoming message content is <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07"><soap:Header><wsa:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Hello</wsa:Action><wsa:MessageID>urn:uuid:4d27bca3-95bf-4341-a51d-51dced508722</wsa:MessageID><wsd:AppSequence InstanceId="19" SequenceId="urn:uuid:85bb4d92-224a-4602-9ba5-bf593806b8a8" MessageNumber="1"></wsd:AppSequence></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:e93d3f92-f8b1-4534-bc13-9dd167758003</wsa:Address></wsa:EndpointReference><wsd:Types>wsdp:Device pub:Computer</wsd:Types><wsd:XAddrs>http://192.168.1.187:5357/e93d3f92-f8b1-4534-bc13-9dd167758003/</wsd:XAddrs><wsd:MetadataVersion>2</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2023-05-21 21:25:01,657:wsdd DEBUG(pid 6182): unhandled action http://schemas.xmlsoap.org/ws/2005/04/discovery/Hello/urn:uuid:4d27bca3-95bf-4341-a51d-51dced508722
2023-05-21 21:25:01,857:wsdd DEBUG(pid 6182): known message (urn:uuid:4d27bca3-95bf-4341-a51d-51dced508722): dropping it
2023-05-21 21:25:02,260:wsdd DEBUG(pid 6182): known message (urn:uuid:4d27bca3-95bf-4341-a51d-51dced508722): dropping it
2023-05-21 21:25:02,742:wsdd DEBUG(pid 6182): known message (urn:uuid:4d27bca3-95bf-4341-a51d-51dced508722): dropping it

I'm curious what's going wrong and why does this fix it and why all the "known message" and "dropping it" in the output messages? One difference to observe when it works and doesn't work is... 887:wsdd INFO(pid 6182): 192.168.1.187:59212(eth0) - - "Probe urn:... vs 933:wsdd INFO(pid 2268): [fe80::5801:cc50:46af:57c7]:61017(eth0) - - "Probe urn:...

Anyway, at least I have a working work-around. Thank you @christgau.

Cheers,

Flex

christgau commented 1 year ago

Ipv6 address below fe80::5801:cc50:46af:57c7 (ipv4=192.168.1.187) is the ip address of the Win 10 VM in Virtualbox, and the output shows responses like "known message" and "dropping it". Why is this?

[...] I'm curious what's going wrong and why does this fix it and why all the "known message" and "dropping it" in the output messages?

That's intentionally and caused by how the protocol works on top of unreliable UDP datagrams. Essentially, repeatedly received messages are just ignored ("dropped"). That's nothing you should care about.

One difference to observe when it works and doesn't work is... 887:wsdd INFO(pid 6182): 192.168.1.187:59212(eth0) - - "Probe urn:... vs 933:wsdd INFO(pid 2268): [fe80::5801:cc50:46af:57c7]:61017(eth0) - - "Probe urn:...

That's indeed strange, but I suspect the IPv6 networking might be not working 100% perfect. I'm not sure how the network settings for your VM look like but maybe there's an issue. Since, the WSD protocol works only with link local addresses (or at least wsdd does so), it may depend on how networking between the host and VMs is setup. On the other hand, you already see a message from a link local sender, but I wonder why there's no further interaction going on.

Thus, you could give IPv6-only for wsdd a chance (wsdd.py -6 ...). If you are interested you may also run tcpdump/wireshark to see if there are messages flying around.

Anyway, at least I have a working work-around. Thank you @christgau.

You're welcome.

Feel also free to close this issue if you found the workaround is sufficient for you.

FlexMcMurphy commented 1 year ago

Hi Steffen,

I'm not sure why I have to do it this way but it's working for me now if I start up wsdd by specifying the interface on the device running wsdd and to instruct it to only use ipv4.

sudo /usr/bin/wsdd --shortlog -i eth0 -4

I never had to do it that way before but maybe something changed in my LAN config I'm not even aware of.

Cheers,

Flex