From owner-freebsd-questions@FreeBSD.ORG Thu May 26 01:06:27 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D18C16A41C for ; Thu, 26 May 2005 01:06:27 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 128C443D1D for ; Thu, 26 May 2005 01:06:27 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 33E5B5131A; Wed, 25 May 2005 18:07:14 -0700 (PDT) Date: Wed, 25 May 2005 18:07:13 -0700 From: Kris Kennaway To: Viren Patel Message-ID: <20050526010713.GA92954@xor.obsecurity.org> References: <1282.66.25.129.27.1117067480.squirrel@mail.cm.utexas.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline In-Reply-To: <1282.66.25.129.27.1117067480.squirrel@mail.cm.utexas.edu> User-Agent: Mutt/1.4.2.1i Cc: freebsd-questions@freebsd.org Subject: Re: NFS broken after upgrading to 5.4 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2005 01:06:27 -0000 --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 25, 2005 at 07:31:20PM -0500, Viren Patel wrote: > Hello all. I have several FreeBSD clients connecting to a > FreeBSD NFS server via a private gigabit LAN for backup > purposes. Both clients and server has IPFW with all > traffic between clients and server allowed on the private > LAN. All clients and the server were running > 5.3-RELEASE-p10 with IPFW, and NFS was working just fine. > Then I upgraded all clients to 5.4-RELEASE-p1 and the NFS > was working fine. Finally I upgraded the NFS server to > 5.4-RELEASE-p1 and now NFS has stopped working. The > clients experience RPC timeouts: >=20 > RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out >=20 > My NFS server rc.conf has the following as per manual: >=20 > nfs_server_enable=3D"YES" > rpcbind_enable=3D"YES" > mountd_flags=3D"-r" >=20 > Clients have: >=20 > nfs_client_enable=3D"YES" >=20 > IPFW rules amount to: >=20 > allow all from NFS_SERVER to NFS_CLIENT in via INTERNAL_IF > allow all from NFS_CLIENT to NFS_SERVER out via INTERNAL_IF >=20 > and appear at the top of the ruleset. Double check this, then triple-check it, because a local configuration difference like this is likely to be your cause. > Obviously something has changed in the NFS system under > 5.4 Not that I can think of. Kris --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFClSFAWry0BWjoQKURAvUnAKC4KuRca/SIWE2ubWLS91oVC1SDcACfSSrV STuAVibKS8SUl9gULCa+9+s= =tP7T -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr--