Date: Tue, 21 Oct 2003 09:39:57 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: Problems with NFS (client) under 5.1. Message-ID: <20031021163957.GA66248@rot13.obsecurity.org> In-Reply-To: <Pine.NEB.3.96L.1031021123049.31330B-100000@fledge.watson.org> References: <20031021120918.GC15345@genius.tao.org.uk> <Pine.NEB.3.96L.1031021123049.31330B-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 21, 2003 at 12:32:12PM -0400, Robert Watson wrote: >=20 > On Tue, 21 Oct 2003, Josef Karthauser wrote: >=20 > > I'm trying to set a FreeBSD 5.1 machine up as an NFS client. The > > server is on an SGI box. Things are strange: >=20 > Any chance you could grab a copy of ethereal and do a bit of on-the-wire > inspection of the RPCs? It would be interesting to know which of the > requests are serviced out of the client cache, and which make it to the > server. It would also be interesting to see if you can see failures in > the wire protocol, or if they're purely an artifact of the client. >=20 > Also, can you confirm the Linux and FreeBSD clients are both using the > same version of NFS with similar protocol settings (i.e., NFSv3 over UDP). Does Linux do NFSv3 yet? I thought that at least until recently there were stability issues and it was recommended it not be used. Kris --DocE+STaALJfprDB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/lWFdWry0BWjoQKURAvplAKDQ6j7JNVHpjTZMGNlvnHwKLp3x0wCgzyTK kGBIwjDdgO32OTYiPvY9i3g= =KLkc -----END PGP SIGNATURE----- --DocE+STaALJfprDB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031021163957.GA66248>