other settings are/were: rw for admin and my user; local permissions (that’s the term the guy in your link was referring to): administrator rw, users ro.
I just tried the line you’ve posted, still the same.
@sam_nazarko Tom is right, I’m not mounting via fstab.
Have you tried adding the NFS share to sources.xml or directly, instead of browsing? Browsing won’t always work properly. You could just copy sources from your old Pi 2 if used there.
If copying sources.xml to the vero has now now let you browse the shares, what I suggested is no longer required; I wouldn’t worry about the error. I hadn’t thought of trying Sam’s solution.
Just for the record, and for future reference, I read up on the Kodi site about using NFS on Kodi becasue it might always have its own little wrinkles. Here’s what it says about sharing NFS from Linux:
A basic configuration for exporting a path with NFS looks like this:
/nfs/export <ip or iprange which is allowed to connect>(rw,all_squash,insecure)
The important options here for use with Kodi are the “ip or iprange” and the “insecure” options. The “insecure” option is needed because we want to be able to run Kodi without root privileges. If the insecure option is not enabled, only the root user (uid 0) will have access to the nfs share. The “ip or iprange” specifies which hosts on the network will be allowed to access the exported NFS share.
And here’s what the Debian (and Fedora) man page says about the insecure option:
secure This option requires that requests originate on an Internet port less than IPPORT_RESERVED (1024). This option is on by default. To turn it off, specify insecure.
So, AFAICT, the insecure option has absolutely nothing to do with allowing non-root access and everything to do with allowing access to a port number >=1024. The Kodi documentation seems to be wrong - but everyone on the Kodi forum was religiously following this instruction. Its effect is fortunately benign but it’s still wrong.
After that you have to change permissions for the folder via File Station.
Open File Station, right click on the folder you want to use as NFS share and choose properties.
Select the Permission tab, and click create > and select Everyone from the list in User or Group, and check what what permissions you want, I choose Read and Write.
The second part was not necessary on earlier Versions of the DSM, but it has to be done now, even though it might be a security risk.
Thats all you have to do to get NFS working, I did not edit any files,.
Details please, guys @thansen_dk@michael47. Which DSM versions are you talking about? Such information is important.
I’ve negotiated access to a Synology box but it’s stuck on DSM 5.1 and the latest version is now 6.1. So it’ll be important to see if there are any significant differences between the two versions WRT NFS.
I started with Vero 2 and Synology 5.1 , when I remember right basicly the same way.
EDIT:
And I’ve spend time to search on OSMC, Kodi, and Google to play with and found the solution for my case.
Now I’m with Vero4 and DSM 6.1.
For first debugging I think
try first to see the NAS in the KODI nfs share, when not, you have a NAS configuration problem = check the link from Thomas.
Edit:
I don’t touch my NAS (production and backup) to try to make a new How-To, but if somebody with a fresh install try to write it, I’m happy to help (in my free time)
For Synology User
Synology work’s a lot for new security features.
I’ve disabled the auto update feature in Synology. I only look mnually for updates for the same DSM Version, and take a look to the changelog…
And take care with major updates (with number changes like 6.0 - 6.1) Wait a little bit,and take a look to the different forums of you third partys appliactions, like DVBLink or others.
Something else: I only concentrated on the video section and I had problems problems with adding the music folder. The permissions had to be set like in the link Tom mentioned: http://forum.kodi.tv/printthread.php?tid=201201&page=2
Otherwise it didn’t work.
I’m also using DSM 6.1.1-15101 Update 2, my Diskstation is a DS415+.
Thanks for the feedback guys. It’s good to have a record of what actually worked.
I’ve just had a play with my friend’s DS210j, which is pretty ancient and runs DSM 5.2 but seemed to work just fine on the tests that I threw at it. I’ll write up my findings in a day or two.