Re: Why does struct sock have saddr and daddr?

Alan Cox (alan@lxorguk.ukuu.org.uk)
Sat, 22 Aug 1998 02:47:36 +0100 (BST)

> I was following up an idea I had, and I wanted to know why struct
> sock has:
>
> __u32 daddr;
> __u32 saddr; /* Sending source */
> __u32 rcv_saddr; /* Bound address */

daddr = destination
saddr = sending address of our end
rcv_saddr = address we bind to

saddr and rcv_saddr may be different as rcv_saddr may be broadcast or
multicast. We do not however use the broadcast/multicast but the interface
address as the source of our packet

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html