Skip to content
Discussion options

You must be logged in to vote

Thanks for the detailed report!

This is a known Windows multicast binding difference — Linux lets you bind directly to the multicast group address, Windows doesn't and expects binding to INADDR_ANY (0.0.0.0) or the local interface address, then joining the multicast group separately.

Quick workaround — force the interface explicitly (replace with your actual LAN IP):

set HDDS_MULTICAST_IF=192.168.1.100
set HDDS_UNICAST_IF=192.168.1.100
set RUST_LOG=hdds=debug
hello_world.exe

The RUST_LOG=hdds=debug will show exactly which interfaces are detected and where the binding fails — that'll help narrow it down.

If that doesn't help, could you share:

  • Windows version
  • Number of network interfaces (…

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@ahenshaw
Comment options

Answer selected by ahenshaw
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants