Hi there! You'll need to use a newer copy of Ganesha that has PROXY_V3
built in. The old proxy is only an NFSv4 proxy. You're almost there, but
you need to use PROXY_V3 with a modern-ish Ganesha (and
use_privileged_client_port isn't an option, because NFSv3 doesn't usually
allow that). I just rewrote the instructions at:
 
https://github.com/nfs-ganesha/nfs-ganesha/wiki/PROXY_V3-and-PROXY_V4
if you have any feedback!
On Tue, Nov 2, 2021 at 2:51 PM Matthew Hess <mxhess(a)gmail.com> wrote:
 I'm currently using the centos 7 distribution and the
centos-nfs-ganesha30
 repo:
 # rpm -q -a | grep nfs-ganesha
 nfs-ganesha-vfs-3.5-2.el7.x86_64
 nfs-ganesha-3.5-2.el7.x86_64
 nfs-ganesha-proxy-3.5-2.el7.x86_64
 centos-release-nfs-ganesha30-1.0-2.el7.centos.noarch
 I've come across a strange need to get a nfsv3 share on a netapp talking
 with a client that only understands nfsv4. I think I'm heading in the right
 direction here but I'm having some trouble getting this setup for testing.
 In the log I am getting:
 init_export_root :EXPORT :CRIT :Lookup failed on path, ExportId=20
 Path=/prod FSAL_ERROR=(Permission denied,13)
 and it appears to give up on the /prod share
 my export config is:
 EXPORT {
   Export_Id = 20;
   Path = "/prod";
   Pseudo = "/prod";
   Access_Type = RW;
   Squash = No_Root_Squash;
   Transports = "TCP";
   FSAL {
     Name = proxy;
     Srv_Addr = <netapp ip>;
     Use_Privileged_Client_Port = false;
   }
 }
 I am able to mount the netapp share from this same system and manage the
 content of the share:
 mount -v -t nfs -o proto=tcp,vers=3,nolock <netapp ip>:/prod /prod
 not certain what I'm doing wrong, can anyone clue me in?
 _______________________________________________
 Support mailing list -- support(a)lists.nfs-ganesha.org
 To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org