From owner-freebsd-net Mon May 21 11: 2: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id CAE1637B422 for ; Mon, 21 May 2001 11:02:01 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA08653; Mon, 21 May 2001 14:01:54 -0400 (EDT) (envelope-from wollman) Date: Mon, 21 May 2001 14:01:54 -0400 (EDT) From: Garrett Wollman Message-Id: <200105211801.OAA08653@khavrinen.lcs.mit.edu> To: Ian Dowse Cc: freebsd-net@FreeBSD.ORG Subject: Re: Using connect() on UDP RPC client sockets. In-Reply-To: <200105211856.aa41143@salmon.maths.tcd.ie> References: <20010521172419.A672@crow.dom2ip.de> <200105211856.aa41143@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > I think the option should be renamed to something like IP_SENDSRCADDR > just to avoid confusion - does this seem reasonable? I think it's OK to add an additional name for the same control message, but it should be possible (and documented) to use the exact control message as was returned from recvmsg() as argument to sendmsg(). -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message