From owner-freebsd-questions@FreeBSD.ORG Tue Apr 24 13:33:20 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4557C16A400 for ; Tue, 24 Apr 2007 13:33:20 +0000 (UTC) (envelope-from dcasey@debtresolve.com) Received: from debtresolve.com (ip175-18.wp-ny-us.debtresolve.com [66.236.175.18]) by mx1.freebsd.org (Postfix) with ESMTP id 0714C13C489 for ; Tue, 24 Apr 2007 13:33:19 +0000 (UTC) (envelope-from dcasey@debtresolve.com) Received: from dummy.name; Tue, 24 Apr 2007 09:33:19 -0400 Message-ID: <462E06BA.4060001@debtresolve.com> Date: Tue, 24 Apr 2007 09:31:38 -0400 From: Dan Casey User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Erik Norgaard References: <462D26B4.4040807@debtresolve.com> <20070424093748.M87543@strange.locolomo.org> In-Reply-To: <20070424093748.M87543@strange.locolomo.org> X-Enigmail-Version: 0.94.3.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: NFS without rpcbind? 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: Tue, 24 Apr 2007 13:33:20 -0000 That makes more sense. Actually I do not care if it is tcp or udp, so long as the ports are not dynamically assigned. I'll have to give what you said a try. Up until now I thought there was now way to do this without dynamic ports. Erik Norgaard wrote: > On Mon, 23 Apr 2007, Dan Casey wrote: > >> It was my understanding that NFS worked off of RPC. I accidently >> stumbled upon some redhat docs that said you use TCP based NFS which >> will not require rpc? I think this is an NFSv4 feature, but I'm not >> sure. I would like to achieve this using FreeBSD 6.2. My goal that I'm >> trying to accomplish is to get nfs to work in an environment where all >> traffic is denied by default. Using rpcbind doesn't work well with that >> type of setup. >> >> I tried the following >> nfs_reserved_port_only="YES" >> nfs_server_enable="YES" >> nfs_server_flags="-t -n 4 -h 10.a.b.c" >> >> This spawned rpcbind which I didn't want. Does anyone know how to do a >> tcp only nfs implimentation? > > AFAIK nfs v4 is not done yet, the client side is but not the server > side. But FBSD do have a tcp based nfs. This doesn't however change > anything with respect to avoiding rpcbind. > > RPC is used to tell the client at which port the daemons bind. These > may be assigned dynamically (I think mountd is dynamic but nfsd static > to 2049). Basically the client connects to the rpcbind deamon to > request which ports the mountd and nfsd are on. > > You can force both to bind to a static port. > > rpcbind_enable="NO" # Run the portmapper service (YES/NO). > nfs_server_enable="YES" # This host is an NFS server (or NO). > mountd_enable="YES" # Run mountd (or NO). > mountd_flags="-r -p 59" # Force mountd to bind on port 59 > > will force mountd to bind to port 59. Then it should be possible to > run the nfs server without rpcbind, but I don't remember how to > configure the client side. > > Cheers, Erik