NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
How does a Linux user logon to their account on a Readynas
ReadyNas Rn104 - Firmware: OS 6.10.3 ReadyCloud: Enabled Share protocols enabled: SMB, NFS, AFP, HTTP
Environment: Linux home network. All devices running Linux Mint 19.3 or 20
A few months ago, I was given 2 x RN104 devices, one of which has 4 x 2TB drives and the other 4 x 4TB drives. I have only just really got around to trying to use them in anger and have foud this the most frustrating experienc in all my 37 years of working with computers.
I am trying to set the devices up with user accounts for the family so that each has a set of home folders which they can use to back-up their computers. I can set up the user accounts easily enough but for the life of me cannot find out how they log on to their accounts in order to populate their home folders.
I can share and mount the existing default folders over NFS no problem, but does not acieve the required result.
This link states:
"Note: A user's home folder will only be created when that user accesses the ReadyNAS for the first time using his or her account."
Fine, but I can find no documentation or posts anywhere that explains how a user is to log onto their account.
I have tried accessing the ReadyNas using http://IP address/share which only gives any results at all when http access is enabled and then it merely displays an FTP list of files. No login window is displayed.
The only login window that is ever displayed is the Admin login window, never the "user" login window.
I have tried setting up Readycloud & MyNetgear accounts to enable remote access with no success.
All the support documentation says is: (From Memory) Users normally access their data via network shares... which is again, not the required result.
I really cannot understand why the setup I want is so hard to achieve. It would have thought that that this would be what most users would expect.
I realise that this product is now obsolete, but if anyone could help, I would be most grateful
Thanks to all for your helpful responses.
Unfortunately, all they have done is confirmed my opinion that the ReadyNas is NOT suitable for the Linux environment. I don't see why Iit should be necessary to install Samba on every machine on the network simply to access a ReadyNas, which is after all a Linux device.
I have instead decided to abandon the ReadynNas and install the drives in a JBOD enclosure driven by a Raspbery Pi. I can acheive everything I want to much more easily.
It's a shame, as I was given 2 of these boxes which, had they been more flexible, could have proved useful.
Thanks again and goodbye
14 Replies
Strictly stick with SMB (and e.g. FTP if desperately required) - there is an authentication in place ... Windows and Apple users do the same, and most Linux desktop distributions do the very same. Most what you read in the ReadyNAS (and many other NAS vendors) features like the home share and other features in documentation are based on this. User and Group based access control and configuration are a snap like this.
Unless your are willing to learn NFS bottom up and manage all your U**x-like systems accordingly, probably in combination with an LDAP server, learn to understand that NFS(v3) does not work based on authentication but much more on GID and UID of the system where the exported NFS shares are mounted. There is no "NFS just works" - almost all home and many small business Linux environment using NFS are a mess. Unless you have all UID, GID, usernames, and much more in sync over all systems, NFS user and group based access will never work correct.
What may be frustrating you (and does for a lot of users, Netgear should change this) is that the user folders are not created until the user has logged into the NAS the first time. You can, of course, log in that first time for them. So, you may not be seeing them because they don't yet exist.
Frankly, though, I find the automatic user folders to be inadaquate and recommend they only be used by those who need them such as for Mac TimeMachine and environments (esp. with Active Directory) where the number of users just makes anything else difficult. Some significant items to me are that the usage of them is not displayed in the admin GUI, they do not support RSYNC for backup, and you just have less control over them individually. Their time of creation is an additional annoyance.
So, since you just need folders for your family, you can create some like any other share and set the access yourself. Note, however, that they cannot have the same name (including with changes in upper/lower case) as the user. So for user John, just create JohnShare, or somesuch.
Nibbles0522 wrote:
I can find no documentation or posts anywhere that explains how a user is to log onto their account.
First of all, you should consider if you really want to use home folders. They are a bit of a pain. If you don't want people to see the home folders of other family members, then you probably should use them. But if you don't care about that, then you are better off using public share. You can still restrict access if you like.
But to answer your question: The home folder is created when you access the NAS with SMB using the user's credentials.
Nibbles0522 wrote:I can find no documentation or posts anywhere that explains how a user is to log onto their account.
Any authenticated access - SMB, FTP, AFP, SSH, and to the admin Web UI (only for members of the admin group as there is no user login on http(s)) - is considered a login _and_ does create the "username" home folder.
NFSv3 and the simple NFSv4 on the other hand (leaving the fully blown NFSv4 implementation with my big friend Kerberos alone) does not need any authentication - it's all UID/GID/exports access based.
StephenB wrote:First of all, you should consider if you really want to use home folders. They are a bit of a pain. If you don't want people to see the home folders of other family members, then you probably should use them.
That's exactly what the home folders here on ReadyNAS are designed for. Unfortunately - and different from the big NAS makers - e.g. admin's can't get access as a folder e.g. by SMB for administrative tasks). These are private folders, not shared folders.
A member of the admin group on can (of course) enumerate and access these folders in the admin Web UI - but not by SMB, AFP. When using FTP, even admin can only see /home/admin - neither admin nor other members of the admin group will be able to gain access.When allowing SSH access to a user why ever, he will be able to enumerate the folders in /home but won't be able to access these thanks to the very basic U**x protection in place by default:
stephenssh@RN516:~$ ls -als /home
total 4
0 drwxr-xr-x 1 admin admin 160 Nov 17 2014 .
4 drwxr-xr-x 1 root root 296 Mar 3 22:28 ..
0 drwx------ 1 admin admin 18 Aug 9 2013 admin
0 drwx------ 1 anyotheruser users 60 Dec 5 2019 anyotheruser
...0 drwx------ 1 stephen users 0 Jul 16 09:29 stephen
0 drwx------ 1 stephenssh users 0 Jul 16 09:43 stephenssh
...
stephenssh@RN516:~$ cd ../anyotheruser
-bash: cd: ../anyotheruser: Permission deniedIn the ReadyNAS scope, this is perfectly correct.
schumaku wrote:
StephenB wrote:
First of all, you should consider if you really want to use home folders. They are a bit of a pain. If you don't want people to see the home folders of other family members, then you probably should use them.
That's exactly what the home folders here on ReadyNAS are designed for. Unfortunately - and different from the big NAS makers - e.g. admin's can't get access as a folder e.g. by SMB for administrative tasks). These are private folders, not shared folders.
The annoying lack of access by admin's is why I said "probably".
But perhaps more on target, I suspect most home NAS users don't really need private folders (and might not want them for their kids). Personally I keep them turned off.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
