How to set options for a nfs share?
Options
![jba](https://us.v-cdn.net/6029482/uploads/avatarstock/nW2K7KBVBE0HN.png)
jba
Posts: 2
Freshman Member
![](https://www.zyxel.com/library/assets/zyxel-forum/freshman_member.png)
I have a nsa310 which runs the nfs package with some shares. However, I am unable to set options (like insecure) to the shares. Is there any way to do this from the gui?
It is possible to change /etc/exports from command line and add the needed options. However, when I change anything from the gui, the added options will be overridden.
jba
#NAS_November
It is possible to change /etc/exports from command line and add the needed options. However, when I change anything from the gui, the added options will be overridden.
jba
#NAS_November
0
Comments
-
Hi @jba
I tried before, modify the configuration files under /etc, after reboot the configuration will be reset automatically, so I think there are the default configuration files saved and would be loaded during booting.
But for option, do you mean set privillage on the NFS folder to limit user's access?0 -
In my case I can modify /etc/exports and the changes are not touched after rebbot.
No, I dont want to limit user access. The problem is that I run Kodi which should access a nfs share. As Kodi has an builtin nfs client and runs not as root on my android device, it cannot use ports smaller than 1024. However, by default the nfs server will publish on a privileged port < 1024. The option insecure tells the nfs server to run on a port >1024 so that a userspace client can access.
However, there may be other option I might like to change in my shares. Would be nice to have a more simple and direct way to do so.
Juergen0 -
OK, maybe some of /etc files would be changed after reboot.
But I think there is no way to change port for NFS, because no GUI option and CLI, besides I know Kodi supports samba protocol, maybe you can use samba protocol on your Kodi to play media files.
0 -
The /etc directory is in the initrd, which is a ramdrive which is fresh on each boot. So the whole /etc directory is reset on reboot.
A flash partition is mounted on /etc/zyxel, and this partition contains all persistent settings, which are not package related. The firmware backend reads a database stored in /etc/zyxel/ and adapts /etc/passwd and /etc/samba/smb.conf accordingly.
The packages maintain their own settings, on firmwares <5.0 in /usr/local/zy-pkgs.
The /etc/exports file actually is a symlink to /usr/local/zy-pkgs/etc/exports, which is created by the nfs start script /usr/local/zy-pkgs/etc/init.d/nfs.
The webinterface only supports a small subset of the nfs possibilities. When editing the nfs shares, it reads the /usr/local/zy-pkgs/etc/exports file, ignores everything is doesn't know about, and writes a fresh one.
So if you want a custom exports file, just edit it, and don't touch the webinterface anymore. Or edit the startscript to create a different symlink to your own private exports file, and synchronize that manually with the output of the webinterface.
1
Categories
- All Categories
- 384 Beta Program
- 2.1K Nebula
- 117 Nebula Ideas
- 80 Nebula Status and Incidents
- 5.1K Security
- 79 USG FLEX H Series
- 247 Security Ideas
- 1.3K Switch
- 69 Switch Ideas
- 910 WirelessLAN
- 34 WLAN Ideas
- 5.9K Consumer Product
- 209 Service & License
- 335 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 1.9K FAQ
- 898 Nebula FAQ
- 415 Security FAQ
- 234 Switch FAQ
- 205 WirelessLAN FAQ
- 46 Consumer Product FAQ
- 137 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 73 About Community
- 62 Security Highlight