From owner-freebsd-current Sun Aug 6 17:37:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id RAA25283 for current-outgoing; Sun, 6 Aug 1995 17:37:16 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA25271 for ; Sun, 6 Aug 1995 17:37:14 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id RAA04944 for freebsd-current@FreeBSD.org; Sun, 6 Aug 1995 17:36:56 -0700 From: "Rodney W. Grimes" Message-Id: <199508070036.RAA04944@gndrsh.aac.dev.com> Subject: Re: workaround for talk's address problem To: freebsd-current@FreeBSD.org Date: Sun, 6 Aug 1995 17:36:55 -0700 (PDT) In-Reply-To: <199508061603.SAA07779@uriah.heep.sax.de> from "J Wunsch" at Aug 6, 95 06:03:27 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1219 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 > for machines where not all interfaces are reachable from the Internet. > This is often the case for the typical dialup user: he's got a SLIP > interface with (e.g.) 111.222.111.33, and an ethernet interface with > 192.168.3.4. The call to gethostbyname() will cause the name server > to return 192.168.3.4 as the first address (since the name server > believes this is the `most local' one), so talk will only be able to > contact hosts inside the (not externally routed) 192.168.3 network. ... The correct fix here is to do what ftp, telnet or any other TCP cleint does, go to the next address if an error or timout occurs on the current address. When we get to the end of the list of addresses, then exit the program with an error. Adding options to force a negotiation address is not going to make the users happy, but the above surely well. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD