Setting up an NFS server: Difference between revisions

From Alpine Linux
m (fixed minor wiki tag issues)
m (bin name: exports -> exportfs)
 
Line 14: Line 14:


After editing /etc/exports, reload your setting
After editing /etc/exports, reload your setting
{{Cmd|# exports -afv}}
{{Cmd|# exportfs -afv}}


To make NFS server service to autostart on boot:
To make NFS server service to autostart on boot:
Line 59: Line 59:


After editing /etc/exports, reload your setting
After editing /etc/exports, reload your setting
{{Cmd|# exports -afv}}
{{Cmd|# exportfs -afv}}


User id mapping is managed by nfsidmap.
User id mapping is managed by nfsidmap.

Latest revision as of 12:21, 26 September 2024

Installation

Install the following package for both NFS client and NFS server service.

# apk add nfs-utils

Configuration

Setting up NFS service on Alpine Linux is no different from other Linux distributions.

NFS Server

Setup export dirs in /etc/exports. For example:

Contents of /etc/exports

/data 10.10.10.0/24(rw,nohide,no_subtree_check,no_root_squash)

After editing /etc/exports, reload your setting

# exportfs -afv

To make NFS server service to autostart on boot:

# rc-update add nfs

To start NFS server service now

# rc-service nfs start

NFS Client

To mount NFS shares automatically, an entry needs to made to /etc/fstab. To mount nfs share from /etc/fstab file at booting of the system

# rc-update add nfsmount

To mount the nfs shares from /etc/fstab file now:

# rc-service nfsmount start

# rc-update add netmount

You can check your boot services:

# rc-status

# rc-service netmount start

Kerberos Authentication

By default, NFS security only validates the IP of the client. You can add user level authentication with a Kerberos installation (MIT KRB5 or Heimdal). It is recommended to have the same Kerberos flavor across the network as both implementations are not completely mutually compatible.

Server Configuration

Assuming you setup Kerberos in the in the network, create ticket to your NFS machine (examples are in MIT KRB5 syntax):

# kadmin: addprinc -randkey nfs/nfs1.example.com@EXAMPLE.COM

And add it to the machines krb5.keytab file:

# kadmin: ktadd nfs/nfs1.example.com@EXAMPLE.COM

Then, edit your /etc/exports, and add sec=krb5 (only authentication), sec=krb5i (also hmac signing) or sec=krb5p (also encryption). For example:

Contents of /etc/exports

/data 10.10.10.0/24(rw,nohide,no_subtree_check,sec=krb5p,no_root_squash)

After editing /etc/exports, reload your setting

# exportfs -afv

User id mapping is managed by nfsidmap.

Client Configuration

In order for the client to connect to NFS via kerberos, enable and start rpc.gssd.

# rc-update add rpc.gssd

# rc-service rpc.gssd start

see Also