From owner-freebsd-net Thu Sep 23 1:51:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 6FB54158A6 for ; Thu, 23 Sep 1999 01:51:34 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id KAA18687; Thu, 23 Sep 1999 10:51:33 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 0288FD236; Thu, 23 Sep 1999 10:51:32 +0200 (CEST) Message-ID: <19990923105131.A99097@enst.fr> Date: Thu, 23 Sep 1999 10:51:31 +0200 From: Pierre Beyssac To: "N. C. Hong" , freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD 3.2 bug when calling connect on a UDP socket? References: <000201bf058f$b27c0e40$0200000a@gchunghome> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <000201bf058f$b27c0e40$0200000a@gchunghome>; from N. C. Hong on Wed, Sep 22, 1999 at 11:48:51PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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