Cygwin 1.5.18: Problem using setsockopt() for multicast

2006-08-16 Thread Alessandro Saffiotti
RSHIP by hardcoding either 5 (winsock1) or 12 (winsok2), but I get the same behavior. I run Cygwin 1.5.18 on Windows XP pro SP2. Any hints? Thanks! Alessandro Saffiotti -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html

Re: Re: Cygwin 1.5.18: Problem using setsockopt() for multicast

2006-08-17 Thread Alessandro Saffiotti
Thanks for the prompt reaction! On Thu, 17 Aug 2006, Corinna Vinschen wrote: > > On Aug 17 01:42, Alessandro Saffiotti wrote: > > > > I have also read the discussion about the conflicting values for > > constants between winsock1 and winsock2. I have tried to replace

RE: Cygwin 1.5.18: Problem using setsockopt() for multicast

2006-08-17 Thread Alessandro Saffiotti
On Thu, 17 Aug 2006, Brian Ford wrote: > > Oh yeah, you must call the setsockopt below after the bind on windows. > Search MSDN for why. Thanks a lot, this actually fixed my problem. In case it may help someone else: I also need to make the socket reusable by setsockopt(tcp_broadcast_receiver,

RE: Cygwin 1.5.18: Problem using setsockopt() for multicast

2006-08-17 Thread Alessandro Saffiotti
On Thu, 17 Aug 2006, Brian Ford wrote: > > > and I have found that this, contrary to the IP_ADD_MEMBERSHIP case, > > must be called BEFORE I bind the socket! > > Um, that makes sense, doesn't it? I guess it does. I just wanted to mention it since the sentence "Note that it is necessary to bin