Disclaimer: ID mapping without a Kerberos server only works halfway with NFSv4, it seems. I managed to get the correct usernames to show up on my client when listing files, but creating new files always creates them as user nobody because the Synology doesn’t map anything in that case. This bug report and the linked thread suggest this is normal behaviour of idmapd when not using Kerberos for some reason. (EDIT: More detailed explanation.)
However, what I did:
First, you have to enable idmapping after loading the NFS service. For that, you have to edit the file /usr/syno/etc/rc.sysv/S83nfsd.sh on the Synology. Find the line
SYNOLoadModules $KERNELMODULEand add the following line after that:
echo "N" > /sys/module/nfsd/parameters/nfs4_disable_idmappingThen, still on the Synology, edit the /etc/idmap.conf and set the Domain to your ITET-PHO if not already set. Disable NFS, apply and re-enable (+apply) it afterwards in the Synology’s control centre to reload nfds.
On your client machine, create a file /etc/modprobe.d/nfs-idmap.conf with the following contents:
options nfs nfs4_disable_idmapping=0
options nfsd nfs4_disable_idmapping=0Reload the nfs kernel module afterwards to apply the options.
Also make sure, idmapd is running on your client. (On Ubuntu artful, I had to run sudo systemctl start nfs-idmapd manually, I think.) And, of course, use nfsvers=4 as a mount option.
(On the Synology, you can killall idmapd and run it in foreground using idmapd -f -vvv to see if it’s doing anything.)
Thanks for writing this up; it’s exactly what I was looking for. After a reboot, however, the value of `/sys/modules/nfs/parameters/nfs4_disable_idmapping` is still Y. Do you suppose something has changed and now there’s a new place where that `echo` command should be run?
Either that or the module loading takes a second and the parameter is not yet available when the echo runs. You could experiment with e.g. a `sleep 2` between `SYNOLoadModules` and the `echo`.