wsdd-rs
http://www.w3.org/2003/05/soap-envelope & SOAP 1.1: http://schemas.xmlsoap.org/soap/envelope/ (Notice trailing slash)XSD validation:
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/2003/05/soap-envelope http://www.w3.org/2003/05/soap-envelope
http://schemas.xmlsoap.org/ws/2005/04/discovery http://schemas.xmlsoap.org/ws/2005/04/discovery/ws-discovery.xsd"
147c9039630afd2bc6a73f1a04d5e6526947d90b (https://github.com/christgau/wsdd/commits/master/)Online spec: https://specs.xmlsoap.org/ws/2005/04/discovery/ws-discovery.pdf (also stored in ./documentation/ws-discovery)
More definitions: https://learn.microsoft.com/en-us/windows/win32/wsdapi/discovery-and-metadata-exchange-message-patterns
Interoperability tool: https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/wsdapi-basic-interoperability-tool
recv_socket RECEIVES multicast messages, SENDS unicast, by binding to the multicast address, on the WSD Portmc_send_socket SENDS multicast messages, on a custom port, RECEIVES unicastuc_send_socket is used REPLY with unicast, it is bound to the interface's address, on the WSD PortThe sockets are separate for a reason: https://github.com/christgau/wsdd/commit/ee8783ce71a408a3d9923b5d67659f7ce2712166
mc_send_socket receives messages in WSDClient, because it sends out a probe over the mc_send_socket, and hosts reply FROM 3072 (in our case uc_send_socket TO the mc_send_socket, that port)
Hello without Xaddr, to which we respond with a Resolve, we get a resolve FROM the host?MIT, see LICENSE
SPDX-License-Identifier: MIT
Content type
Image
Digest
sha256:a57011759…
Size
6.5 MB
Last updated
about 7 hours ago
docker pull kristofmattei/wsdd-rs:edge