From owner-freebsd-current  Sun Aug  6 14:04:29 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id OAA05946
          for current-outgoing; Sun, 6 Aug 1995 14:04:29 -0700
Received: from crash.ops.neosoft.com (crash.ops.NeoSoft.COM [198.64.212.50])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id OAA05939
          for <freebsd-current@FreeBSD.org>; Sun, 6 Aug 1995 14:04:27 -0700
Received: (from smace@localhost) by crash.ops.neosoft.com (8.6.11/8.6.10) id QAA07313; Sun, 6 Aug 1995 16:04:31 -0500
From: Scott Mace <smace@crash.ops.neosoft.com>
Message-Id: <199508062104.QAA07313@crash.ops.neosoft.com>
Subject: Re: workaround for talk's address problem
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Sun, 6 Aug 1995 16:04:30 -0500 (CDT)
Cc: freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de
In-Reply-To: <18450.807740189@time.cdrom.com> from "Jordan K. Hubbard" at Aug 6, 95 01:16:29 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 501       
Sender: current-owner@FreeBSD.org
Precedence: bulk

> 
> > talk(1) has problems with multi-homed hosts.  To negotiate the
> > connection with the remote peer, it uses the first address as returned
> > by a call to gethostbyname().  This will cause the connection to hang
> 
> NFS has the exact same problem, FWIW.  If there's a more general
> solution, we should go for it.
> 
> 						Jordan
> 

INN uses the full list of ip's returned and will accept connections from
either, but that really doesn't help that much in this situation I think...

	Scott