From owner-freebsd-arch Mon Mar 4 7: 7:10 2002 Delivered-To: freebsd-arch@freebsd.org Received: from nimbus.nj.caldera.com (nimbus.nj.caldera.com [132.147.103.56]) by hub.freebsd.org (Postfix) with ESMTP id E673C37B400 for ; Mon, 4 Mar 2002 07:07:01 -0800 (PST) Received: from caldera.com (bird [132.147.135.198]) by nimbus.nj.caldera.com (8.10.1/UW7.1.1-NSCd) with ESMTP id g24F6gI26406; Mon, 4 Mar 2002 10:06:42 -0500 (EST) Message-ID: <3C838D82.A9CEA74B@caldera.com> Date: Mon, 04 Mar 2002 10:06:42 -0500 From: Sergey Babkin Organization: Caldera International, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Tony Finch Cc: chawla@caldera.com, arch@freebsd.org Subject: Re: proposition for new socket syscalls {send,recv}fromto References: <20020303195801.A17586@chiark.greenend.org.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tony Finch wrote: > > I agree that these calls are necessary and should have been presend from > the start, but you seem to be unaware of the usual way of implementing > UDP servers that are aware of multihoming, such as BIND. They typically > use SIOCGIFADDR to read the list of interfaces on the machine then bind > a socket to each one. The server can choose the appropriate socket to > use according to the source address that is required. However this > doesn't deal all that well with a dynamically changing list of interface > addresses... Hm, from looking at the BIND code it seems to reload the list of interfaces periodically, so it can handle the changing list of interfaces. And it has a fair amount of code dealing with it. But not all the servers do this: for instance, tftpd does not. -SB -- Sergey Babkin sergey@caldera.com Escalations Research Group, Caldera - NJ (908)790-2385 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message