On 06/15/17 21:34, Doug Ortega wrote:
Frank,
Turns out that the nfs-ganesha proxy client was using a source port >
1024 for the nfs client connection to the server. I added the
'insecure' option to export in /etc/exports on the server to allow
client connections from an unreserved source port. This let me get
past the issue with the NFS4ERR_PERM being returned on the lookup.
Doug
------------------------------------------------------------------------------
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
Hi Doug,
By default, it's true that the nfs-ganesha proxy client is using a
source port > 1024 to connect the background nfs server. You have an
option to change this. If you want the proxy client use a privileged
port, you should use the Use_Privileged_Client_Port option as this :
PROXY
{
Remote_Server
{
Srv_Addr=192.168.1.30;
Use_Privileged_Client_Port = true;
}
}
Let me know if you are facing any problem by using this option. I will
be happy to try to fix it.
Regards
--
Patrice LUCAS
Ingenieur-Chercheur, CEA-DAM/DSSI/SISR/LA2S
tel : +33 (0)1 69 26 47 86
e-mail : patrice.lu...@cea.fr
------------------------------------------------------------------------------
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
