From owner-freebsd-current  Sun Aug  6 15:28:40 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id PAA12173
          for current-outgoing; Sun, 6 Aug 1995 15:28:40 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id PAA12163
          for <freebsd-current@freebsd.org>; Sun, 6 Aug 1995 15:28:36 -0700
Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.11/8.6.5) with ESMTP id PAA07702; Sun, 6 Aug 1995 15:27:48 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id PAA00290; Sun, 6 Aug 1995 15:29:20 -0700
Message-Id: <199508062229.PAA00290@corbin.Root.COM>
To: Mark Murray <mark@grondar.za>
cc: freebsd-current@freebsd.org (FreeBSD-current users)
Subject: Re: workaround for talk's address problem 
In-reply-to: Your message of "Mon, 07 Aug 95 00:05:28 +0200."
             <199508062205.AAA08363@grumble.grondar.za> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sun, 06 Aug 1995 15:29:19 -0700
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.
>
>Paul Traina fixed a similar problem with kadmin(d?) from eBones a
>couple of days ago.

   What is the problem with specifying INADDR_ANY for the local address?

-DG