From owner-freebsd-net Thu Sep 23 22:17:36 1999 Delivered-To: freebsd-net@freebsd.org Received: from sttlpop5.sttl.uswest.net (sttlpop5.sttl.uswest.net [206.81.192.5]) by hub.freebsd.org (Postfix) with SMTP id 355F014D71 for ; Thu, 23 Sep 1999 22:17:23 -0700 (PDT) (envelope-from nchong@uswest.net) Received: (qmail 7110 invoked by alias); 24 Sep 1999 05:16:59 -0000 Delivered-To: fixup-freebsd-net@FreeBSD.ORG@fixme Received: (qmail 7099 invoked by uid 0); 24 Sep 1999 05:16:58 -0000 Received: from ddslppp190.sttl.uswest.net (HELO gchunghome) (216.160.75.190) by sttlpop5.sttl.uswest.net with SMTP; 24 Sep 1999 05:16:58 -0000 From: "N. C. Hong" To: "'Pierre Beyssac'" , Subject: RE: FreeBSD 3.2 bug when calling connect on a UDP socket? Date: Thu, 23 Sep 1999 22:21:02 -0700 Message-ID: <000301bf064c$992e6920$0200000a@gchunghome> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <19990923105131.A99097@enst.fr> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org That shouldn't matter. I don't have to join the UDP socket to a multicast group in order to simply do a sendto of a UDP datagram to that multicast group. Regardless, the behavior still exists even if I explicitly join the UDP socket to the multicast group. Ultimately, I desire to use the more efficient send call to the multicast endpoint by calling connect first. But as the program demonstrates, I am restricted to one doing this from one process per host. -----Original Message----- From: Pierre Beyssac [mailto:beyssac@enst.fr] Sent: Thursday, September 23, 1999 1:52 AM To: N. C. Hong; freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD 3.2 bug when calling connect on a UDP socket? On Wed, Sep 22, 1999 at 11:48:51PM -0700, N. C. Hong wrote: > On FreeBSD 3.2, when running two instances of the following program, the > second instance fails during the connect call. It works fine on Windows NT. > I haven't tested on other platforms. I don't see any reason why two UDP > sockets bound to the same port on the same host can't both be "connected" to > a multicast endpoint. Apparently, you haven't given any indication to the system that you want to connect to a multicast endpoint. You have to use socket option IP_ADD_MEMBERSHIP. See man ip(4). -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message