FREENAS CIFS PERMISSIONS HOW TO

FREENAS CIFS PERMISSIONS HOW TO

In this article, we will teach you how to create a shared folder/drive, that can be accessed from all SMB-supported operating systems (mostly Microsoft Windows).īefore you start, you will have to make sure FreeNAS is properly installed on your server with at least one available hard disk. I would rather not keep using the vers=1.0 kluge I would prefer to do this correctly.One of the most useful features for a FreeNAS server is the sharing files over the network. I know there's supposed to be a mapping performed by cifs.idmap and winbindd, but I haven't figured out exactly how that's done or how to set it up. I can actually create, modify, and delete files in the share, but they appear as root-owned. But now the UIDs are wrong, and everything looks like it's owned by root. r-xr-xr-x 1 root root 0 Apr 21 00:09 R-XR-XR-Xĭespite the options file_mode=0755,dir_mode=0755 still being injected, the permissions are now appearing correctly. rwxr-xr-x 1 root root 0 Apr 21 00:08 RWXR-XR-X However, when I add the mount option cifsacl: sudo mount.cifs -o 'user=me,noperm,multiuser,cifsacl' //freenas/me $HOME/mntĪnd enter my credentials for the server via the cifscreds command, I get these results: //freenas/me on /home/me/mnt type cifs ls -al mnt/testdir/ Since my ultimate goal is to have several concurrent users all connecting to their own home directories with their own credentials, I started experimenting with this mount incantation, specifically the multiuser option: sudo mount.cifs -o 'user=me,noperm,multiuser' //freenas/me ls -al mnt/testdir/ I have not yet figured out where these unwanted options are coming from. Something has injected file_mode=0755,dir_mode=0755 into the mount options, and the resulting permissions are 0x755 on all files, regardless of their actual permissions, which is obviously wrong. However, if I do not explicitly specify vers=1.0, then this happens: //freenas/me on /home/me/mnt type cifs ls -al mnt/testdir/ However, the mount is forcing SMB version 1.0, which is old and busted. And our test directory shows up with the following modes/permissions: ls -al mnt/testdir/ Once done, the following entry appears in the mtab: //freenas/me on /home/me/mnt type cifs (rw,relatime,vers=1.0,cache=strict,username=me,domain=,uid=1000,forceuid,gid=1000,forcegid,addr=X.X.X.X,soft,unix,posixpaths,serverino,mapposix,acl,rsize=1048576,wsize=65536,echo_interval=60,actimeo=1) (The above is actually normally performed by autofs, but that turns out to be not relevant.) The current mount incantation looks something like this: sudo mount.cifs -o 'vers=1.0,username=me,uid=me,gid=me,credentials=]' //freenas/me $HOME/mnt The client is a Debian Sid (unstable) system with Samba v4.7.4 components, and cifs-utils version 6.8-1. It is basically running in standalone/workgroup mode there is no AD/domain controller, and I don't want one if I can avoid it. The server is a FreeNAS system running Samba 4.7.0.

The problem is that I can't get files on the CIFS share to show correct permissions on the Linux client without forcing vers=1.0 in the mount options.

Freenas cifs permissions