> I was able to access the server from the ganesha machine using the normal > NFS client. There is only a problem when I try to use the proxy. > The configuration on the server and the client connection test using normal > NFS client are shown below. > > On server: > > # exportfs -v > export/test > 192.168.1.0/24(rw,async,wdelay,no_root_squash,no_subtree_check,sec=sys > ,rw,no_root_squash,no_all_squash) > > On client: > > $ sudo mount -v -t nfs4 192.168.1.30:/export/test /mnt/test > $ mount | grep 1.30 > 192.168.1.30:/export/test on /mnt/test type nfs4 > (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto > =tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.9,local_lock= > none,addr=192.168.1.30)
Hmm, ok, that all looks good and the Ganesha config looks good. Maybe Patrice can chime in, having not actually run PROXY myself, I'm at a loss to how to continue... Frank > > What is the export path on the remote server (192.168.1.30)? If you > > mount it directly using the kernel nfs client, can you mount > > 192.168.1.30:/ and see /mnt/export? What security flavors is the remote > server export using? > > > > Frank > > > > > > --- > > This email has been checked for viruses by Avast antivirus software. > > https://www.avast.com/antivirus > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
