[lkml]   [1998]   [Aug]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Why does struct sock have saddr and daddr?
> 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
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.046 / U:9.456 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site