nfs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
nfs [2020/01/19 09:12]
Stephane de Labrusse [Custom rules] 		nfs [2020/12/21 18:42]
Stephane de Labrusse [Usage]
Line 18: Line 18:
      
 ==== Usage ==== ==== Usage ====
 +
 The rpm installs nethserver-samba and nethserver-ibay, nfs is running and adjustable per ibay via the sharedfolder panel. It is advised to install nethserver-dc (Samba AD) to protect by a password  the access via Samba, however nfs can work also if the share are in guest mode. The rpm installs nethserver-samba and nethserver-ibay, nfs is running and adjustable per ibay via the sharedfolder panel. It is advised to install nethserver-dc (Samba AD) to protect by a password  the access via Samba, however nfs can work also if the share are in guest mode.
  
Line 23: Line 24:
  
 * Use the server UID/GID server **(access control by GID and IP)**  * Use the server UID/GID server **(access control by GID and IP)** 
- 
 In this mode the users of the remote client must be in the same GID that the owning group of the samba share. In this mode the users of the remote client must be in the same GID that the owning group of the samba share.
 You must add manually to all users the GID as a secondary group You must add manually to all users the GID as a secondary group
- 
 Any root users of any remote clients can overwrite this GID limitation, hence the option root squash to restrict the root power. Any root users of any remote clients can overwrite this GID limitation, hence the option root squash to restrict the root power.
- 
 In clear you have two access control (GID and IP) In clear you have two access control (GID and IP)
  
 * Lazzy mode **(access control by IP)** * Lazzy mode **(access control by IP)**
- 
 Uncheck the option above, then you don't need to set a second gid on users, the only access control is at the IP level Uncheck the option above, then you don't need to set a second gid on users, the only access control is at the IP level
- 
 If you want you can allow quickly a read access to all your local network (you must respect the gid if checked) If you want you can allow quickly a read access to all your local network (you must respect the gid if checked)
  
Line 131: Line 127:
 <file> <file>
 * use the wildcard '*' * use the wildcard '*'
-* open your shares to ip(s) outside of your local network(s) 
 * use a domain to define your shares, the ip or the network are a mandatory * use a domain to define your shares, the ip or the network are a mandatory
 * use the root '/' * use the root '/'