Re: connect(2) for UDP

Jackson, Craig (Gale) wrote:
> > the problem is not that easy... if server has two interfaces
> > configured server reply from a single interface so it can happen that
> > client ask to an interface with a given IP but server reply from
> > another IP, in such situation with connect used recv don't receive
> > server reply :( I think we can solve this problem using two sockets,
> > one connected and another not connected.
> 
> Good point -- we had a server with three IPs on one network, so it could
> have 3 web server instances each listening on port 80.  The source
> address of the SNMP UDP packets would end up being round-robined.

Is this a theory, or observed behavior?  

If I send a message to a port at an address, I more or less expect an
answer back from the same place.  Even if each machine in the cluster
listens to 1434, the internal cluster logic has to be simpler if each
machine answers its own queries....

--jkl