X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: Cygwin 1.5.18: Problem using setsockopt() for multicast Date: Thu, 17 Aug 2006 14:48:42 +0100 Message-ID: <00cf01c6c203$da04b5b0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 17 August 2006 14:45, Brian Ford wrote: > On Thu, 17 Aug 2006, Alessandro Saffiotti wrote: > >> I ran into the following problem when using setsockopt to create a >> multicast receiver in my own application. Here is the relevant part of >> the code: >> >> tcp_broadcast_receiver = socket(PF_INET,SOCK_DGRAM,IPPROTO_IP); >> >> memset(&imreq, 0, sizeof(struct ip_mreq)); >> imreq.imr_multiaddr.s_addr = inet_addr("227.1.3.5"); >> imreq.imr_interface.s_addr = INADDR_ANY; > > INADDR_ANY is in host byte order, but you need network order for this > call. Yeh, that's it! And don't forget to use left-handed bits - the ordinary right-handed ones are no good for INADDR_ANY. :) cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/