X-Spam-Check-By: sourceware.org Date: Thu, 17 Aug 2006 16:29:09 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Cygwin 1.5.18: Problem using setsockopt() for multicast Message-ID: <20060817142909.GI20467@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <00cf01c6c203$da04b5b0$a501a8c0@CAM.ARTIMI.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Aug 17 09:06, Brian Ford wrote: > My point should have been that I use this construct every day in 1.5.18 > and 1.5.21 within our application and it works fine. I saw very few > differences. Here is my snippet in case I missed something else obvious: > > fd = socket(AF_INET, SOCK_DGRAM, 0); > > Oh yeah, you must call the setsockopt below after the bind on windows. > Search MSDN for why. Uh, that's the important clue! I didn't know that and would have been puzzled by this and found the relevant article in MSDN only after hours of debugging. Thanks for the information, it's pretty valuable. Corinna P.S.: Do you know the MSDN articel off-hand, maybe? -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/