From owner-freebsd-current Mon Aug 7 02:15:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id CAA25939 for current-outgoing; Mon, 7 Aug 1995 02:15:44 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id CAA25933 for ; Mon, 7 Aug 1995 02:15:40 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id CAA22698; Mon, 7 Aug 1995 02:15:27 -0700 To: "Rodney W. Grimes" cc: freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: workaround for talk's address problem In-reply-to: Your message of "Mon, 07 Aug 1995 00:13:34 PDT." <199508070713.AAA00579@gndrsh.aac.dev.com> Date: Mon, 07 Aug 1995 02:15:26 -0700 Message-ID: <22696.807786926@time.cdrom.com> From: "Jordan K. Hubbard" 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. > > NFS does not have such a problem, or at least I have never seen it, and > I have _lots_ of networks, all but 1 serving NFS: I can reproduce this easily. Just take my gateway box and make both of its addresses, the "lower numbered one for slip" and the "higher one for local subnet", use the same name. Then try to NFS mount something from one of the private subnet hosts - it will fail since DNS returns the entry for the slip line, not the ethernet. I bit myself with this and have since gone to separate hostnames for each interface. Jordan