Impact of bind() on recvfrom() and sendto()

Assume a UDP socket S on a machine with more than one interface card,
let's say two interface cards with IP addresses IP1 and IP2.
Also assume that you bind the socket S to IP1 and port P1.

Does it mean that recvfrom() on socket S will not receive any data
that came in
on interface card with IP2 for port P1?

Does it mean that sendto() will send all datagrams through interface
card with IP1
regardless of the target address? What if this conflicts with the
route table?

(E-Mail Removed) <(E-Mail Removed)> wrote:
> Assume a UDP socket S on a machine with more than one interface
> card, let's say two interface cards with IP addresses IP1 and IP2.
> Also assume that you bind the socket S to IP1 and port P1.

> Does it mean that recvfrom() on socket S will not receive any data
> that came in on interface card with IP2 for port P1?

When a UDP datagram arrives, it will be handed to the UDP endpoint
with the closest match on local/remote IP, local/remote port -
_without_ any conflicting fields.

> Does it mean that sendto() will send all datagrams through interface
> card with IP1 regardless of the target address? What if this
> conflicts with the route table?

All it does in this context is specify the source IP.

rick jones
--
The glass is neither half-empty nor half-full. The glass has a leak.
The real question is "Can it be patched?"
these opinions are mine, all mine; HP might not want them anyway...
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...