[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-net
Subject:    RE: FreeBSD 3.2 bug when calling connect on a UDP socket?
From:       "N. C. Hong" <nchong () uswest ! net>
Date:       1999-09-24 5:21:02
[Download RAW message or body]

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

[prev in list] [next in list] [prev in thread] [next in thread]