[svlug] NFS mount problem

[Mark]

Brian,

Thanks for the response.
I don't want user-authentication, I just thought that specifying a uid parameter might fix my original permission problem.

So I guess the question really is why I am getting the the "Permission denied" error.
I have seen the IP-based access control and added the whole 192.168.1.0/24 subnet for r/w access, so that should not be it...
I'll play around with it some more...

Thanks,

MARK
 

> -----Original Message-----
> From: svlug-bounces+msalists=gmx.net at lists.svlug.org 
> [mailto:svlug-bounces+msalists=gmx.net at lists.svlug.org] On 
> Behalf Of Brian J. Tarricone
> Sent: Friday, February 22, 2008 5:56 PM
> To: svlug at lists.svlug.org
> Subject: Re: [svlug] NFS mount problem
> 
> Mark wrote:
> > 
> > I have a problem with mounting an NFS share.
> > I have a NetGear ReadyNAS 1100 with NFS enabled and user configured.
> > The user's UID is set to 2001.
> > 
> > I am trying to mount the share using:
> > mount  -t nfs 192.168.1.8:/test1 /mnt/test1
> > and get a "mount: 192.168.1.8:/test failed, reason given by 
> server: Permission denied".
> > 
> > This is ok, because the NAS is configured to require a user ID.
> > 
> > But when I try to add a user ID by doing this:
> > mount  -t nfs -o uid=2001 192.168.1.8:/test1 /mnt/test1
> > then I get "unknown nfs mount parameter: uid=2001"
> 
> I think you're misunderstanding how NFS works.  Aside from 
> Kerberos-based authentication (not supported on the ReadyNAS, IIRC), 
> there's no user authentication with NFS.  It's entirely 
> host-based.  In 
> the NFS config on the NAS, you have to tell it the IP addresses of 
> clients that are allowed access (you can specify separate 
> read-only and 
> read/write hosts).
> 
> The UID is meaningless in the authentication sense, though to make it 
> easy to edit files as your regular user on the client 
> (assuming you give 
> read/write access to the client), it's best to sync the UID 
> of your user 
> account on the client with the UID that owns the files on the 
> NFS server.
> 
> If you want a way to access the NAS that requires a user name and 
> password, you'll have to use AFP or SMB, though you lose UNIX 
> permissions and file ownership that way, unfortunately.
> 
> Alternatively, if you're willing to get your hands a bit 
> dirty, you can 
> enable ssh access on the ReadyNAS (possibly only if you're 
> using the 4.x 
> firmware series, I don't recall), and then you can use sshfs 
> (via FUSE) 
> from the client to mount arbitrary directories.  Of course, with this 
> method, you'll get rather poor performance because the CPU in the 
> ReadyNAS isn't designed for doing encryption[1].
> 
> 	-brian
> 
> [1] I don't recall where I read this, so I might be wrong, but I hear 
> blowfish is the 'easiest' cipher (computationally) out of 
> those that ssh 
> supports.  If that's really the case, you could pass
> '-o Ciphers=blowfish-cbc' to sshfs to get a slight performance boost.
> 
> _______________________________________________
> svlug mailing list
> svlug at lists.svlug.org
> http://lists.svlug.org/lists/listinfo/svlug
>