[Spread-users] Bug in Spread for Windows?

Jonathan Stanton jonathan at cnds.jhu.edu
Tue Nov 14 04:00:26 EST 2006


I have not seen this problem before and we do use windows occasionally, so it 
should work.

In your spread.conf file, did you configure any specific interfaces for the hosts 
in your Spread_segment? Or did you just list one IP for each machine? (The reason 
I ask is that if you specify specific interfaces, that causes the binds to be done 

Are you sure that broadcast packets normally work on your machine (you can ping the 
broadcast address for your network and get replies from many other machines)? You 
can also replace the broadcast address in spread.conf with an IP multicast address 
and try that. Let us know if that works while broadcast doesn't.

If you can also let us know exactly what version of windows you are using and how 
you built spread (or where you got the binaries)



On Fri, Nov 03, 2006 at 01:14:57PM +0200, Michael Chelnokov wrote:
> Hello,
> Spread tries to bind a socket to a broadcast address to receive broadcast packets within a segment. It is needed for UNIX systems, but it is not allowed on Windows systems, WinSock error 10049 (WSAEADDRNOTAVAIL) is occured during startup. The error occured both in 3.17.3 release and in 4.0.0 release candidate 2.
> I think it is possible to just enclose appropriate code in Net_init routine to #ifndef ARCH_PC_WIN95/#endif. Hope the problem will be solved in 4.0.0 release.
> Best regards,
> Michelnok.
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users

Jonathan R. Stanton         jonathan at cs.jhu.edu
Dept. of Computer Science   
Johns Hopkins University    

More information about the Spread-users mailing list