FreshTomato Wiki

FreshTomato's NFS server lets you create and modify fileshares to NFS clients (mainly Unix-like systems). Network File System (NFS) is a distributed file system protocol. It allows users on a client device to access files over a network, similar to the way local storage is accessed.

It's essentially the equivalent of Samba in a Linux environment.

Enable NFS Server: sets the NFS server process to start at boot time.

Enable legacy (NFS V2) support: enables support for NFS version 2.

NFS currently has 3 versions - NFS 2/3/4. FreshTomato defaults to v3, but can also be set to “speak” v2 also.

Exports

Directory: specifies the filesystem location to be shared over the network.

IP Address/Subnet: limits connectivity to the IP address or subnet you specify here.

Access: defines the share permissions (how the share can be accessed).

• Read-only
• Read/Write

Sync/Async:

• Synchronous - FreshTomato will only acknowledge data after it's been written out

• Async(hronous) - FreshTomato will acknowledge data before it's been written out.
  The NFS server will acknowledge data before it's committed to disk.
  If the server crashes, this can lead to data corruption.

Subtree Check:

• No * - subtree check will be disabled.
• Yes - enables subtree checking.

This has minor security implications, but can improve reliability in some scenarios.

In NFS, if a filesystem subdirectory is exported, but not the whole filesystem, then whenever a NFS request arrives, the server must check the accessed file is in the appropriate filesystem (easy) and that it is in the exported tree (harder). This check is called the subtree_check.

To perform the check, the server must include details of the file location in the file handle given to the client. This can cause problems accessing files that are renamed while a client has them open. However, in many simple cases, it will still work.

Other Options: here, you can enter advanced options.

Please refer to official NFS documentation for details. NFS man(ual) page