Date: Tue, 18 Aug 1998 14:54:34 -0400 From: Robert Withrow <witr@rwwa.com> To: Nick Hibma <nick.hibma@jrc.it> Cc: FreeBSD hackers mailing list <hackers@FreeBSD.ORG> Subject: Re: kern/2858: FreeBSD NFS client can't mount filesystem from dual-homed machine Message-ID: <199808181854.OAA21569@spooky.rwwa.com> In-Reply-To: Your message of "Tue, 18 Aug 1998 18:15:43 %2B0200." <Pine.GSO.3.95q.980818180314.7644B-100000@elect8>
next in thread | previous in thread | raw e-mail | index | archive | help
nick.hibma@jrc.it said: :- The problem is that the client sends a request to the 'far' address :- but gets an answer from the 'nearby' address and waits indefinitely :- for an answer. I think this is a bug, but not with FreeBSD. I'm guessing that host A is a Sun system, or something like it, right? It is a *security* problem to accept the response from a different IP address than the one you sent it to, otherwise someone could sniff and masquerade as the NFS server. I think it a *bug* for the server to respond with the "near" address, and I think it would be a *bug* to accept this bogus address by default. Anyway, I overcame this problem (using automount) by specifying the "noconn" mount flag, as in: /defaults opts:=nosuid,grpid,rsize=8192,wsize=8192,noconn,rw,hard,intr; Try that. --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808181854.OAA21569>