Send multicast to multiple interface for discover hosts

[Mario156090]

Hello, I have a laptop with multiple network interfaces, I need to discover share folders for every networks. So I am checking the traffic using wireshark and I can watch the multicast discover only for the WAN interface, and it's because WAN interface has the default gateway, so only discover another hosts in that interface but does not discover others hosts in another networks directly connected.

If I add a static route for multicast traffic for example for LAN2 using "sudo ip route add 239.255.255.250/32 dev virbr2" I can see the hosts on LAN2 but stop discover every on WAN.

Network 1 - WAN - wlan0
192.168.3.0/24
Network 2 LAN2 - virbr0:
192.168.122.1.0/24
Network 3 LAN 3 - virbr2:
192.168.120.0/24:

So, my question is, is possible config WSDD for send multicast discover for two or three interfaces same time?

I tried the -H option but does not work for me.

[christgau]

How do you launch wsdd? What are the command line arguments you use?

By design, wsdd is able to handle multiple interfaces. Have you checked the -i option? From the readme:

-i INTERFACE/ADDRESS, --interface INTERFACE/ADDRESS
Specify on which interfaces wsdd will be listening on. If no interfaces are specified, all interfaces are used.

[Mario156090]

How do you launch wsdd? What are the command line arguments you use?

By design, wsdd is able to handle multiple interfaces. Have you checked the -i option? From the readme:

-i INTERFACE/ADDRESS, --interface INTERFACE/ADDRESS
Specify on which interfaces wsdd will be listening on. If no interfaces are specified, all interfaces are used.

Hello, yes, but there is no traffic using that option.

[christgau]

How do you launch wsdd? What are the command line arguments you use?

[Mario156090]

How do you launch wsdd? What are the command line arguments you use?

Here you can see.

[christgau]

Ok, but what do you expect if you explicitly limit traffic to virbr2? Try without any -i option.

If that does not help, stop the wsdd daemon for a moment and launch wsdd manually using wsdd -vv (and no additional arguments) and post the output here.

[Mario156090]

I expect discover hosts on virbr2.

wsdd -vv                                                                                                                                                                                                    /usr/bin/wsdd:1876: DeprecationWarning: There is no current event loop
  asyncio.get_event_loop().set_debug(True)
2025-02-09 10:54:14,836:wsdd WARNING(pid 15589): no interface given, using all interfaces
2025-02-09 10:54:14,836:wsdd INFO(pid 15589): using pre-defined UUID c3e195f5-cece-40a4-9760-9ae807e243d9
2025-02-09 10:54:14,837:asyncio DEBUG(pid 15589): Using selector: EpollSelector
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): netlink message with 512 bytes
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): RTM new/del addr family: 2 flags: 128 scope: 254 idx: 1
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): rt_attr 8 1
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): rt_attr 8 2
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): rt_attr 7 3
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): rt_attr 8 8
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): rt_attr 20 6
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): new address 127.0.0.1%lo
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): ignoring that address on lo
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): RTM new/del addr family: 2 flags: 0 scope: 0 idx: 3
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): rt_attr 8 1
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): rt_attr 8 2
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): rt_attr 8 4
2025-02-09 10:54:14,837:wsdd DEBUG(pid 15589): rt_attr 10 3
2025-02-09 10:54:14,838:wsdd DEBUG(pid 15589): rt_attr 8 8
2025-02-09 10:54:14,838:wsdd DEBUG(pid 15589): rt_attr 20 6
2025-02-09 10:54:14,838:wsdd DEBUG(pid 15589): new address 192.168.3.2%wlan0
2025-02-09 10:54:14,838:wsdd DEBUG(pid 15589): handling traffic for 192.168.3.2%wlan0
2025-02-09 10:54:14,838:wsdd INFO(pid 15589): joined multicast group 239.255.255.250 on 192.168.3.2%wlan0
2025-02-09 10:54:14,838:wsdd DEBUG(pid 15589): transport address on wlan0 is 192.168.3.2
2025-02-09 10:54:14,838:wsdd DEBUG(pid 15589): will listen for HTTP traffic on address ('192.168.3.2', 5357)
2025-02-09 10:54:14,838:wsdd DEBUG(pid 15589): 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:1ca444e2-e6fe-11ef-8750-ec2e988443d5</wsa:MessageID><wsd:AppSequence InstanceId="1739116454" SequenceId="urn:uuid:1ca445be-e6fe-11ef-8750-ec2e988443d5" MessageNumber="0" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://192.168.3.2:5357/c3e195f5-cece-40a4-9760-9ae807e243d9</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2025-02-09 10:54:14,838:wsdd INFO(pid 15589): scheduling Hello message via wlan0 to 239.255.255.250%wlan0
2025-02-09 10:54:14,841:wsdd DEBUG(pid 15589): RTM new/del addr family: 2 flags: 128 scope: 0 idx: 4
2025-02-09 10:54:14,842:wsdd DEBUG(pid 15589): rt_attr 8 1
2025-02-09 10:54:14,842:wsdd DEBUG(pid 15589): rt_attr 8 2
2025-02-09 10:54:14,842:wsdd DEBUG(pid 15589): rt_attr 8 4
2025-02-09 10:54:14,842:wsdd DEBUG(pid 15589): rt_attr 8 3
2025-02-09 10:54:14,842:wsdd DEBUG(pid 15589): rt_attr 8 8
2025-02-09 10:54:14,842:wsdd DEBUG(pid 15589): rt_attr 20 6
2025-02-09 10:54:14,842:wsdd DEBUG(pid 15589): new address 192.168.50.2%Pr0
2025-02-09 10:54:14,842:wsdd DEBUG(pid 15589): handling traffic for 192.168.50.2%Pr0
2025-02-09 10:54:14,842:wsdd INFO(pid 15589): joined multicast group 239.255.255.250 on 192.168.50.2%Pr0
2025-02-09 10:54:14,842:wsdd DEBUG(pid 15589): transport address on Pr0 is 192.168.50.2
2025-02-09 10:54:14,842:wsdd DEBUG(pid 15589): will listen for HTTP traffic on address ('192.168.50.2', 5357)
2025-02-09 10:54:14,843:wsdd DEBUG(pid 15589): 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:1ca4ebd6-e6fe-11ef-8750-ec2e988443d5</wsa:MessageID><wsd:AppSequence InstanceId="1739116454" SequenceId="urn:uuid:1ca4ed84-e6fe-11ef-8750-ec2e988443d5" MessageNumber="1" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://192.168.50.2:5357/c3e195f5-cece-40a4-9760-9ae807e243d9</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2025-02-09 10:54:14,843:wsdd INFO(pid 15589): scheduling Hello message via Pr0 to 239.255.255.250%Pr0
2025-02-09 10:54:14,856:wsdd DEBUG(pid 15589): RTM new/del addr family: 2 flags: 128 scope: 0 idx: 5
2025-02-09 10:54:14,857:wsdd DEBUG(pid 15589): rt_attr 8 1
2025-02-09 10:54:14,857:wsdd DEBUG(pid 15589): rt_attr 8 2
2025-02-09 10:54:14,857:wsdd DEBUG(pid 15589): rt_attr 8 4
2025-02-09 10:54:14,857:wsdd DEBUG(pid 15589): rt_attr 11 3
2025-02-09 10:54:14,857:wsdd DEBUG(pid 15589): rt_attr 8 8
2025-02-09 10:54:14,857:wsdd DEBUG(pid 15589): rt_attr 20 6
2025-02-09 10:54:14,857:wsdd DEBUG(pid 15589): new address 192.168.122.1%virbr0
2025-02-09 10:54:14,857:wsdd DEBUG(pid 15589): handling traffic for 192.168.122.1%virbr0
2025-02-09 10:54:14,857:wsdd INFO(pid 15589): joined multicast group 239.255.255.250 on 192.168.122.1%virbr0
2025-02-09 10:54:14,857:wsdd DEBUG(pid 15589): transport address on virbr0 is 192.168.122.1
2025-02-09 10:54:14,857:wsdd DEBUG(pid 15589): will listen for HTTP traffic on address ('192.168.122.1', 5357)
2025-02-09 10:54:14,857:wsdd DEBUG(pid 15589): 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:1ca72d42-e6fe-11ef-8750-ec2e988443d5</wsa:MessageID><wsd:AppSequence InstanceId="1739116454" SequenceId="urn:uuid:1ca72e5a-e6fe-11ef-8750-ec2e988443d5" MessageNumber="2" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://192.168.122.1:5357/c3e195f5-cece-40a4-9760-9ae807e243d9</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2025-02-09 10:54:14,857:wsdd INFO(pid 15589): scheduling Hello message via virbr0 to 239.255.255.250%virbr0
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): RTM new/del addr family: 2 flags: 128 scope: 0 idx: 6
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): rt_attr 8 1
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): rt_attr 8 2
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): rt_attr 8 4
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): rt_attr 11 3
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): rt_attr 8 8
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): rt_attr 20 6
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): new address 192.168.120.1%virbr2
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): handling traffic for 192.168.120.1%virbr2
2025-02-09 10:54:14,871:wsdd INFO(pid 15589): joined multicast group 239.255.255.250 on 192.168.120.1%virbr2
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): transport address on virbr2 is 192.168.120.1
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): will listen for HTTP traffic on address ('192.168.120.1', 5357)
2025-02-09 10:54:14,871:wsdd DEBUG(pid 15589): 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:1ca95658-e6fe-11ef-8750-ec2e988443d5</wsa:MessageID><wsd:AppSequence InstanceId="1739116454" SequenceId="urn:uuid:1ca9577a-e6fe-11ef-8750-ec2e988443d5" MessageNumber="3" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://192.168.120.1:5357/c3e195f5-cece-40a4-9760-9ae807e243d9</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2025-02-09 10:54:14,871:wsdd INFO(pid 15589): scheduling Hello message via virbr2 to 239.255.255.250%virbr2
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): RTM new/del addr family: 2 flags: 128 scope: 0 idx: 7
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): rt_attr 8 1
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): rt_attr 8 2
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): rt_attr 8 4
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): rt_attr 12 3
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): rt_attr 8 8
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): rt_attr 20 6
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): new address 172.17.0.1%docker0
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): handling traffic for 172.17.0.1%docker0
2025-02-09 10:54:14,885:wsdd INFO(pid 15589): joined multicast group 239.255.255.250 on 172.17.0.1%docker0
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): transport address on docker0 is 172.17.0.1
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): will listen for HTTP traffic on address ('172.17.0.1', 5357)
2025-02-09 10:54:14,885:wsdd DEBUG(pid 15589): 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:1cab7c8a-e6fe-11ef-8750-ec2e988443d5</wsa:MessageID><wsd:AppSequence InstanceId="1739116454" SequenceId="urn:uuid:1cab7dd4-e6fe-11ef-8750-ec2e988443d5" MessageNumber="4" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://172.17.0.1:5357/c3e195f5-cece-40a4-9760-9ae807e243d9</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2025-02-09 10:54:14,885:wsdd INFO(pid 15589): scheduling Hello message via docker0 to 239.255.255.250%docker0
2025-02-09 10:54:14,900:wsdd DEBUG(pid 15589): netlink message with 20 bytes
2025-02-09 10:54:14,900:wsdd DEBUG(pid 15589): invalid rtm_message type 3`

[christgau]

This looks good (please paste using according formatting). Now try again with wsdd -D -vv.

Please note that bridges and docker interfaces are known to cause trouble.

[Mario156090]

wsdd -D -vv

This looks good (please paste using according formatting). Now try again with wsdd -D -vv.

Please note that bridges and docker interfaces are known to cause trouble.

`    ~  wsdd -D -vv                                                                                                                                                                                                  ✔  11:06:37 AM  
/usr/bin/wsdd:1876: DeprecationWarning: There is no current event loop
  asyncio.get_event_loop().set_debug(True)
2025-02-09 11:06:41,676:wsdd WARNING(pid 18181): no interface given, using all interfaces
2025-02-09 11:06:41,676:wsdd INFO(pid 18181): using pre-defined UUID c3e195f5-cece-40a4-9760-9ae807e243d9
2025-02-09 11:06:41,676:asyncio DEBUG(pid 18181): Using selector: EpollSelector
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): netlink message with 512 bytes
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): RTM new/del addr family: 2 flags: 128 scope: 254 idx: 1
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): rt_attr 8 1
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): rt_attr 8 2
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): rt_attr 7 3
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): rt_attr 8 8
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): rt_attr 20 6
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): new address 127.0.0.1%lo
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): ignoring that address on lo
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): RTM new/del addr family: 2 flags: 0 scope: 0 idx: 3
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): rt_attr 8 1
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): rt_attr 8 2
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): rt_attr 8 4
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): rt_attr 10 3
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): rt_attr 8 8
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): rt_attr 20 6
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): new address 192.168.3.2%wlan0
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): handling traffic for 192.168.3.2%wlan0
2025-02-09 11:06:41,677:wsdd INFO(pid 18181): joined multicast group 239.255.255.250 on 192.168.3.2%wlan0
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): transport address on wlan0 is 192.168.3.2
2025-02-09 11:06:41,677:wsdd DEBUG(pid 18181): will listen for HTTP traffic on address ('192.168.3.2', 5357)
2025-02-09 11:06:41,678:wsdd DEBUG(pid 18181): 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:d9caf24a-e6ff-11ef-a671-ec2e988443d5</wsa:MessageID><wsd:AppSequence InstanceId="1739117201" SequenceId="urn:uuid:d9caf33a-e6ff-11ef-a671-ec2e988443d5" MessageNumber="0" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://192.168.3.2:5357/c3e195f5-cece-40a4-9760-9ae807e243d9</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2025-02-09 11:06:41,678:wsdd INFO(pid 18181): scheduling Hello message via wlan0 to 239.255.255.250%wlan0
2025-02-09 11:06:44,682:wsdd INFO(pid 18181): scheduling Probe message via wlan0 to 239.255.255.250%wlan0
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): RTM new/del addr family: 2 flags: 128 scope: 0 idx: 4
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): rt_attr 8 1
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): rt_attr 8 2
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): rt_attr 8 4
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): rt_attr 8 3
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): rt_attr 8 8
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): rt_attr 20 6
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): new address 192.168.50.2%Pr0
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): handling traffic for 192.168.50.2%Pr0
2025-02-09 11:06:44,682:wsdd INFO(pid 18181): joined multicast group 239.255.255.250 on 192.168.50.2%Pr0
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): transport address on Pr0 is 192.168.50.2
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): will listen for HTTP traffic on address ('192.168.50.2', 5357)
2025-02-09 11:06:44,682:wsdd DEBUG(pid 18181): 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:db956d62-e6ff-11ef-a671-ec2e988443d5</wsa:MessageID><wsd:AppSequence InstanceId="1739117201" SequenceId="urn:uuid:db956e70-e6ff-11ef-a671-ec2e988443d5" MessageNumber="1" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://192.168.50.2:5357/c3e195f5-cece-40a4-9760-9ae807e243d9</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2025-02-09 11:06:44,682:wsdd INFO(pid 18181): scheduling Hello message via Pr0 to 239.255.255.250%Pr0
2025-02-09 11:06:46,696:wsdd INFO(pid 18181): scheduling Probe message via Pr0 to 239.255.255.250%Pr0
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): RTM new/del addr family: 2 flags: 128 scope: 0 idx: 5
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): rt_attr 8 1
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): rt_attr 8 2
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): rt_attr 8 4
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): rt_attr 11 3
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): rt_attr 8 8
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): rt_attr 20 6
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): new address 192.168.122.1%virbr0
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): handling traffic for 192.168.122.1%virbr0
2025-02-09 11:06:46,696:wsdd INFO(pid 18181): joined multicast group 239.255.255.250 on 192.168.122.1%virbr0
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): transport address on virbr0 is 192.168.122.1
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): will listen for HTTP traffic on address ('192.168.122.1', 5357)
2025-02-09 11:06:46,696:wsdd DEBUG(pid 18181): 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:dcc8bdc4-e6ff-11ef-a671-ec2e988443d5</wsa:MessageID><wsd:AppSequence InstanceId="1739117201" SequenceId="urn:uuid:dcc8be78-e6ff-11ef-a671-ec2e988443d5" MessageNumber="2" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://192.168.122.1:5357/c3e195f5-cece-40a4-9760-9ae807e243d9</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2025-02-09 11:06:46,696:wsdd INFO(pid 18181): scheduling Hello message via virbr0 to 239.255.255.250%virbr0
2025-02-09 11:06:46,711:wsdd INFO(pid 18181): scheduling Probe message via virbr0 to 239.255.255.250%virbr0
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): RTM new/del addr family: 2 flags: 128 scope: 0 idx: 6
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): rt_attr 8 1
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): rt_attr 8 2
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): rt_attr 8 4
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): rt_attr 11 3
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): rt_attr 8 8
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): rt_attr 20 6
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): new address 192.168.120.1%virbr2
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): handling traffic for 192.168.120.1%virbr2
2025-02-09 11:06:46,711:wsdd INFO(pid 18181): joined multicast group 239.255.255.250 on 192.168.120.1%virbr2
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): transport address on virbr2 is 192.168.120.1
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): will listen for HTTP traffic on address ('192.168.120.1', 5357)
2025-02-09 11:06:46,711:wsdd DEBUG(pid 18181): 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:dccb05e8-e6ff-11ef-a671-ec2e988443d5</wsa:MessageID><wsd:AppSequence InstanceId="1739117201" SequenceId="urn:uuid:dccb0692-e6ff-11ef-a671-ec2e988443d5" MessageNumber="3" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://192.168.120.1:5357/c3e195f5-cece-40a4-9760-9ae807e243d9</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2025-02-09 11:06:46,711:wsdd INFO(pid 18181): scheduling Hello message via virbr2 to 239.255.255.250%virbr2
2025-02-09 11:06:47,732:wsdd INFO(pid 18181): scheduling Probe message via virbr2 to 239.255.255.250%virbr2
2025-02-09 11:06:47,732:wsdd DEBUG(pid 18181): RTM new/del addr family: 2 flags: 128 scope: 0 idx: 7
2025-02-09 11:06:47,732:wsdd DEBUG(pid 18181): rt_attr 8 1
2025-02-09 11:06:47,732:wsdd DEBUG(pid 18181): rt_attr 8 2
2025-02-09 11:06:47,732:wsdd DEBUG(pid 18181): rt_attr 8 4
2025-02-09 11:06:47,732:wsdd DEBUG(pid 18181): rt_attr 12 3
2025-02-09 11:06:47,732:wsdd DEBUG(pid 18181): rt_attr 8 8
2025-02-09 11:06:47,732:wsdd DEBUG(pid 18181): rt_attr 20 6
2025-02-09 11:06:47,732:wsdd DEBUG(pid 18181): new address 172.17.0.1%docker0
2025-02-09 11:06:47,732:wsdd DEBUG(pid 18181): handling traffic for 172.17.0.1%docker0
2025-02-09 11:06:47,732:wsdd INFO(pid 18181): joined multicast group 239.255.255.250 on 172.17.0.1%docker0
2025-02-09 11:06:47,732:wsdd DEBUG(pid 18181): transport address on docker0 is 172.17.0.1
2025-02-09 11:06:47,732:wsdd DEBUG(pid 18181): will listen for HTTP traffic on address ('172.17.0.1', 5357)
2025-02-09 11:06:47,733:wsdd DEBUG(pid 18181): 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:dd66d95a-e6ff-11ef-a671-ec2e988443d5</wsa:MessageID><wsd:AppSequence InstanceId="1739117201" SequenceId="urn:uuid:dd66da40-e6ff-11ef-a671-ec2e988443d5" MessageNumber="4" /></soap:Header><soap:Body><wsd:Hello><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsd:XAddrs>http://172.17.0.1:5357/c3e195f5-cece-40a4-9760-9ae807e243d9</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:Hello></soap:Body></soap:Envelope>
2025-02-09 11:06:47,733:wsdd INFO(pid 18181): scheduling Hello message via docker0 to 239.255.255.250%docker0
2025-02-09 11:06:48,748:wsdd INFO(pid 18181): scheduling Probe message via docker0 to 239.255.255.250%docker0
2025-02-09 11:06:48,748:wsdd DEBUG(pid 18181): netlink message with 20 bytes
2025-02-09 11:06:48,749:wsdd DEBUG(pid 18181): invalid rtm_message type 3
2025-02-09 11:06:48,749:wsdd INFO(pid 18181): 192.168.3.2:60143(wlan0) - - "Probe urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde UDP" - -
2025-02-09 11:06:48,749:wsdd DEBUG(pid 18181): 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:de98e460-f98e-49a7-8182-f78c34863fde</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>

2025-02-09 11:06:48,749:wsdd DEBUG(pid 18181): 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:de01fa16-e6ff-11ef-a671-ec2e988443d5</wsa:MessageID><wsa:RelatesTo>urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde</wsa:RelatesTo><wsd:AppSequence InstanceId="1739117201" SequenceId="urn:uuid:de01fb06-e6ff-11ef-a671-ec2e988443d5" MessageNumber="5" /></soap:Header><soap:Body><wsd:ProbeMatches><wsd:ProbeMatch><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</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>
2025-02-09 11:06:48,749:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,749:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,749:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,750:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,750:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,750:wsdd INFO(pid 18181): 192.168.120.225:3702(virbr2) - - "ProbeMatches urn:uuid:ddfee2c1-e6ff-11ef-b5a9-d3a9375b74fa UDP" - -
2025-02-09 11:06:48,750:wsdd DEBUG(pid 18181): 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: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:ddfee2c1-e6ff-11ef-b5a9-d3a9375b74fa</wsa:MessageID><wsa:RelatesTo>urn:uuid:dd66ba56-e6ff-11ef-a671-ec2e988443d5</wsa:RelatesTo><wsd:AppSequence InstanceId="1739115375" SequenceId="urn:uuid:ddfee416-e6ff-11ef-b408-d3a9375b74fa" MessageNumber="6" /></soap:Header><soap:Body><wsd:ProbeMatches><wsd:ProbeMatch><wsa:EndpointReference><wsa:Address>urn:uuid:400526b6-322a-5573-86be-9d9a9e9f0d93</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>
2025-02-09 11:06:48,750:wsdd DEBUG(pid 18181): probe match without XAddrs, sending resolve
2025-02-09 11:06:48,750:wsdd DEBUG(pid 18181): 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/Resolve</wsa:Action><wsa:MessageID>urn:uuid:de021c30-e6ff-11ef-a671-ec2e988443d5</wsa:MessageID></soap:Header><soap:Body><wsd:Resolve><wsa:EndpointReference><wsa:Address>urn:uuid:400526b6-322a-5573-86be-9d9a9e9f0d93</wsa:Address></wsa:EndpointReference></wsd:Resolve></soap:Body></soap:Envelope>
2025-02-09 11:06:48,750:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,750:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,750:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,750:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,750:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,751:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,751:wsdd INFO(pid 18181): 192.168.120.225:3702(virbr2) - - "ResolveMatches urn:uuid:ddff13d5-e6ff-11ef-af1c-d3a9375b74fa UDP" - -
2025-02-09 11:06:48,751:wsdd DEBUG(pid 18181): 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: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:ddff13d5-e6ff-11ef-af1c-d3a9375b74fa</wsa:MessageID><wsa:RelatesTo>urn:uuid:de021c30-e6ff-11ef-a671-ec2e988443d5</wsa:RelatesTo><wsd:AppSequence InstanceId="1739115375" SequenceId="urn:uuid:ddff1480-e6ff-11ef-9988-d3a9375b74fa" MessageNumber="7" /></soap:Header><soap:Body><wsd:ResolveMatches><wsd:ResolveMatch><wsa:EndpointReference><wsa:Address>urn:uuid:400526b6-322a-5573-86be-9d9a9e9f0d93</wsa:Address></wsa:EndpointReference><wsd:Types>wsdp:Device pub:Computer</wsd:Types><wsd:XAddrs>http://192.168.120.225:5357/400526b6-322a-5573-86be-9d9a9e9f0d93</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:ResolveMatch></wsd:ResolveMatches></soap:Body></soap:Envelope>
2025-02-09 11:06:48,751:wsdd DEBUG(pid 18181): resolve match for urn:uuid:400526b6-322a-5573-86be-9d9a9e9f0d93 on http://192.168.120.225:5357/400526b6-322a-5573-86be-9d9a9e9f0d93
/usr/bin/wsdd:649: DeprecationWarning: Testing an element's truth value will always return True in future versions.  Use specific 'len(elem)' or 'elem is not None' test instead.
  if (host_sec):
2025-02-09 11:06:48,758:wsdd INFO(pid 18181): discovered MINT-VIRT in Workgroup:WORKGROUP on 192.168.120.225
2025-02-09 11:06:48,758:wsdd DEBUG(pid 18181): {'FriendlyName': 'WSD Device mint-virt', 'FirmwareVersion': '1.0', 'SerialNumber': '1', 'Manufacturer': 'wsdd', 'ModelName': 'wsdd', 'DisplayName': 'MINT-VIRT', 'BelongsTo': 'Workgroup:WORKGROUP'}
2025-02-09 11:06:48,758:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,759:wsdd DEBUG(pid 18181): known message (urn:uuid:de98e460-f98e-49a7-8182-f78c34863fde): dropping it
2025-02-09 11:06:48,759:wsdd INFO(pid 18181): 192.168.3.2:35183(wlan0) - - "Resolve urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07 UDP" - -
2025-02-09 11:06:48,759:wsdd DEBUG(pid 18181): 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:676a3045-ecba-4bce-b441-96efcb02eb07</wsa:MessageID></soap:Header><soap:Body><n1:Resolve><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference></n1:Resolve></soap:Body></soap:Envelope>

2025-02-09 11:06:48,759:wsdd DEBUG(pid 18181): 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:de0375c6-e6ff-11ef-a671-ec2e988443d5</wsa:MessageID><wsa:RelatesTo>urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07</wsa:RelatesTo><wsd:AppSequence InstanceId="1739117201" SequenceId="urn:uuid:de0376ca-e6ff-11ef-a671-ec2e988443d5" MessageNumber="6" /></soap:Header><soap:Body><wsd:ResolveMatches><wsd:ResolveMatch><wsa:EndpointReference><wsa:Address>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsd:Types>wsdp:Device pub:Computer</wsd:Types><wsd:XAddrs>http://192.168.3.2:5357/c3e195f5-cece-40a4-9760-9ae807e243d9</wsd:XAddrs><wsd:MetadataVersion>1</wsd:MetadataVersion></wsd:ResolveMatch></wsd:ResolveMatches></soap:Body></soap:Envelope>
2025-02-09 11:06:48,759:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,759:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,759:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,759:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,759:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,759:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,760:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,760:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,760:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,760:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,760:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,760:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,760:wsdd DEBUG(pid 18181): known message (urn:uuid:676a3045-ecba-4bce-b441-96efcb02eb07): dropping it
2025-02-09 11:06:48,763:wsdd DEBUG(pid 18181): processing WSD Get message (urn:uuid:43a9ee56-dd4a-4729-9422-a8f1821675ac)
2025-02-09 11:06:48,763:wsdd DEBUG(pid 18181): 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:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:To><wsa:From><wsa:Address>urn:uuid:1637ad6a-a355-4b94-a2d3-2f9c81ec87fb</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:43a9ee56-dd4a-4729-9422-a8f1821675ac</wsa:MessageID></soap:Header><soap:Body/></soap:Envelope>\n'
2025-02-09 11:06:48,764:wsdd DEBUG(pid 18181): 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:de042d86-e6ff-11ef-a671-ec2e988443d5</wsa:MessageID><wsa:RelatesTo>urn:uuid:43a9ee56-dd4a-4729-9422-a8f1821675ac</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 asus-arch</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:c3e195f5-cece-40a4-9760-9ae807e243d9</wsa:Address></wsa:EndpointReference><wsdp:Types>pub:Computer</wsdp:Types><wsdp:ServiceId>urn:uuid:c3e195f5-cece-40a4-9760-9ae807e243d9</wsdp:ServiceId><pub:Computer>ASUS-ARCH/Workgroup:WORKGROUP</pub:Computer></wsdp:Host></wsdp:Relationship></wsx:MetadataSection></wsx:Metadata></soap:Body></soap:Envelope>
2025-02-09 11:06:48,764:wsdd INFO(pid 18181): 192.168.3.2 - - "POST /c3e195f5-cece-40a4-9760-9ae807e243d9 HTTP/1.1" 200 -
2025-02-09 11:06:48,853:wsdd DEBUG(pid 18181): known message (urn:uuid:ddff13d5-e6ff-11ef-af1c-d3a9375b74fa): dropping it
2025-02-09 11:06:48,890:wsdd DEBUG(pid 18181): known message (urn:uuid:ddfee2c1-e6ff-11ef-b5a9-d3a9375b74fa): dropping it`

[christgau]

2025-02-09 11:06:44,682:wsdd INFO(pid 18181): scheduling Probe message via wlan0 to 239.255.255.250%wlan0
2025-02-09 11:06:46,696:wsdd INFO(pid 18181): scheduling Probe message via Pr0 to 239.255.255.250%Pr0
2025-02-09 11:06:46,711:wsdd INFO(pid 18181): scheduling Probe message via virbr0 to 239.255.255.250%virbr0
2025-02-09 11:06:47,732:wsdd INFO(pid 18181): scheduling Probe message via virbr2 to 239.255.255.250%virbr2
2025-02-09 11:06:48,748:wsdd INFO(pid 18181): scheduling Probe message via docker0 to 239.255.255.250%docker0
2025-02-09 11:06:48,750:wsdd INFO(pid 18181): 192.168.120.225:3702(virbr2) - - "ProbeMatches urn:uuid:ddfee2c1-e6ff-11ef-b5a9-d3a9375b74fa UDP" - -
2025-02-09 11:06:48,751:wsdd INFO(pid 18181): 192.168.120.225:3702(virbr2) - - "ResolveMatches urn:uuid:ddff13d5-e6ff-11ef-af1c-d3a9375b74fa UDP" - -
2025-02-09 11:06:48,758:wsdd INFO(pid 18181): discovered MINT-VIRT in Workgroup:WORKGROUP on 192.168.120.225

This looks good as well. Note that messages for discovery (Probe) are sent to all interfaces. If they are not received by the Windows machines on the respective other end, it's not an issue of wsdd.

[Mario156090]

2025-02-09 11:06:44,682:wsdd INFO(pid 18181): scheduling Probe message via wlan0 to 239.255.255.250%wlan0
2025-02-09 11:06:46,696:wsdd INFO(pid 18181): scheduling Probe message via Pr0 to 239.255.255.250%Pr0
2025-02-09 11:06:46,711:wsdd INFO(pid 18181): scheduling Probe message via virbr0 to 239.255.255.250%virbr0
2025-02-09 11:06:47,732:wsdd INFO(pid 18181): scheduling Probe message via virbr2 to 239.255.255.250%virbr2
2025-02-09 11:06:48,748:wsdd INFO(pid 18181): scheduling Probe message via docker0 to 239.255.255.250%docker0
2025-02-09 11:06:48,750:wsdd INFO(pid 18181): 192.168.120.225:3702(virbr2) - - "ProbeMatches urn:uuid:ddfee2c1-e6ff-11ef-b5a9-d3a9375b74fa UDP" - -
2025-02-09 11:06:48,751:wsdd INFO(pid 18181): 192.168.120.225:3702(virbr2) - - "ResolveMatches urn:uuid:ddff13d5-e6ff-11ef-af1c-d3a9375b74fa UDP" - -
2025-02-09 11:06:48,758:wsdd INFO(pid 18181): discovered MINT-VIRT in Workgroup:WORKGROUP on 192.168.120.225

This looks good as well. Note that messages for discovery (Probe) are sent to all interfaces. If they are not received by the Windows machines on the respective other end, it's not an issue of wsdd.

Well, Checking that log I believe you are correct but Why does not show on different file browsers as dolphin, nautilus, nemo, etc?

Is very strange.

Check the network traffic, only send a hello by port 1900.

[christgau]

Well, Checking that log I believe you are correct but Why does not show on different file browsers as dolphin, nautilus, nemo, etc?

Because there are no answers to those "Probe" messages being received, which would be "ProbeMatches" as seen above for the single host that is detected. Since it works for the virbr2 interface, please check virbr0 too. Maybe there is a different configuration that prevents multicasts going out. Pr0 also sounds suspicious. Are there any hosts to be discovery on wlan0?

For the file browsers, I don't know if they actually support WSD, Nautilus does, AFAIK. Maybe a plugin is needed. But for the others I do not know at all.

Anyways, I actually do not see an issue of wsdd.

Check the network traffic, only send a hello by port 1900.

On which host was this recorded? The host that runs wsdd or the other machine that should be discovered.

In addition, Port 1900 is not used by wsdd. That's for SSDP (Simple Service Discovery Protocol, see lower left) traffic your are seeing, not related to WSD.

[Mario156090]

Hello, I reported this with KDE team and I believe they are working for fix this issue inside dolphin.

https://bugs.kde.org/show_bug.cgi?id=496809