From owner-freebsd-hackers  Wed Aug 27 02:55:26 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id CAA23327
          for hackers-outgoing; Wed, 27 Aug 1997 02:55:26 -0700 (PDT)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA23314
          for <hackers@FreeBSD.ORG>; Wed, 27 Aug 1997 02:55:22 -0700 (PDT)
Received: (from danny@localhost)
	by panda.hilink.com.au (8.8.5/8.8.5) id TAA02181;
	Wed, 27 Aug 1997 19:54:57 +1000 (EST)
Date: Wed, 27 Aug 1997 19:54:56 +1000 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Aled Morris <aledm@routers.co.uk>
cc: "Louis A. Mamakos" <louie@TransSys.COM>, hackers@FreeBSD.ORG
Subject: Re: UDP "to" address? 
In-Reply-To: <Pine.BSF.3.91.970826170445.21490H-100000@ns.uk.peer.net>
Message-ID: <Pine.BSF.3.91.970827195353.243B-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


On Tue, 26 Aug 1997, Aled Morris wrote:

> On Tue, 26 Aug 1997, Louis A. Mamakos wrote:
> 
> > Typically, a portable approach to doing this is to create a socket
> > per interface address and bind it.  Then you look at which fd the
> > packet was received on to determine the destination address.
> 
> That sounds like the best way - unfortunately, I'm currently using inetd, 
> so I'll have to do a bit more work...

You could run an inetd per interface address.  See inetd(8) '-a' flag.

Danny