Date: Mon, 7 Aug 1995 00:13:34 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: workaround for talk's address problem Message-ID: <199508070713.AAA00579@gndrsh.aac.dev.com> In-Reply-To: <18450.807740189@time.cdrom.com> from "Jordan K. Hubbard" at Aug 6, 95 01:16:29 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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: gndrsh# nslookup gndrsh.aac.dev.com Server: gndrsh.aac.dev.com Address: 0.0.0.0 Name: gndrsh.aac.dev.com Addresses: 198.145.92.49, 198.145.92.241, 198.145.92.17, 198.145.92.33 mountd gets confused if you add an interface and don't restart it, but other than that and routing path problems it works just fine. It does not have the problem that was described about talk, NFS handles this stuff just fine! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508070713.AAA00579>