Date: Thu, 20 Jul 2000 09:55:19 -0500 From: Dan Nelson <dnelson@emsphone.com> To: Rasmus Skaarup <rasmus@gal.dk> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: NFS client problem (fwd) Message-ID: <20000720095519.A14294@dan.emsphone.com> In-Reply-To: <Pine.BSF.4.21.0007201509290.29024-100000@skaarup.org>; from "Rasmus Skaarup" on Thu Jul 20 15:13:30 GMT 2000 References: <Pine.BSF.4.21.0007201509290.29024-100000@skaarup.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jul 20), Rasmus Skaarup said: > Forgot to mention that I'm running 4.1-RC as of 07/17/2000. > > Furthermore, I tried to run tcpdump while nfs mounting the directory and > got the following output: > > ** > 15:07:31.822231 skaarup.intra.xxx.dk.444806954 > pesto.intra.xxx.dk.nfs: 128 access [|nfs] > 15:07:31.822513 petix.intra.xxx.dk.nfs > skaarup.intra.xxx.dk.444806954: reply ok 120 proc-858862898A > ** > > The request is sent to pesto (the cluster service), but the answer comes > from the host, petix. > > Is this the reason why mount_nfs wont mount the directory? Probably. FreeBSD assumes the reply is a forged packet and ignores it. Two reported workarounds are to use TCP mounts, or to use the "noconn" option when mounting. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000720095519.A14294>