From owner-freebsd-current Mon Aug 7 17:19:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id RAA10327 for current-outgoing; Mon, 7 Aug 1995 17:19:12 -0700 Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA10321 for ; Mon, 7 Aug 1995 17:19:08 -0700 Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id BAA04544 ; Tue, 8 Aug 1995 01:17:55 +0100 To: "Rodney W. Grimes" cc: "Jordan K. Hubbard" , 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 17:02:52 PDT." <199508080002.RAA01756@gndrsh.aac.dev.com> Date: Tue, 08 Aug 1995 01:17:54 +0100 Message-ID: <4542.807841074@palmer.demon.co.uk> From: Gary Palmer Sender: current-owner@freebsd.org Precedence: bulk In message <199508080002.RAA01756@gndrsh.aac.dev.com>, "Rodney W. Grimes" write s: >Okay, I am subnetted 0xfffffff0, .17 is my 10Mb/s ether, .33 and .49 are >2 100Mb/s ethernets. I can nfs mount from any of those three networks >without any problems what so ever. I do it all day long and have been for >over a month with this setup. As Jsutin already stated, you run named on gndrsh, so when a client does a nslookup of gndrsh to find it's address, it'll get the address of the interface it connects to ('cos BIND is like that). However, morton/throck don't run nameservers, who does the nameservice, and hence the address could be returned in a random order. If the slip addr is returned first, then mount will try and contact the slip address. mountd will reply from the ether address and confuse the client. Does this clear things up? :-) Gary