From Fedora Project Wiki
< User:Renich | HowTo
(added zone change for internal interface) |
(updated server section with several changes (sorry)) |
||
| Line 46: | Line 46: | ||
<pre> | <pre> | ||
[General] | [General] | ||
Domain = | Domain = domain.tld | ||
[Mapping] | [Mapping] | ||
| Line 53: | Line 53: | ||
</pre> | </pre> | ||
* | * Enable <code>rpcbind</code>, <code>rpcidmapd</code>, <code>nfslock</code>, and <code>nfs</code> services to start at boot: | ||
<pre> | <pre> | ||
su -c " | su -c "systemctl enable rpcbind.service rpcidmapd.service nfslock.service nfs.service" | ||
</pre> | </pre> | ||
* | * Start those services: | ||
<pre> | <pre> | ||
su -c " | su -c "systemctl start rpcbind.service rpcidmapd.service nfslock.service nfs.service" | ||
</pre> | </pre> | ||
* Edit <code>/etc/exports</code>. Enter your <code>root</code> password when prompted: | * Edit <code>/etc/exports</code>. Enter your <code>root</code> password when prompted: | ||
| Line 90: | Line 68: | ||
* Add your shares here (available to your home network) If you want your shares to be ''read only'', change <code>rw</code> to <code>ro</code> from these statements: | * Add your shares here (available to your home network) If you want your shares to be ''read only'', change <code>rw</code> to <code>ro</code> from these statements: | ||
<pre> | <pre> | ||
/srv/nfs/share1 192.168.1.0/255.255.255.0(rw,async) | |||
/srv/nfs/share1 | /srv/nfs/share2 192.168.1.0/255.255.255.0(ro) | ||
/srv/nfs/share2 | /srv/nfs/share3 192.168.1.0/255.255.255.0(rw) | ||
/srv/nfs/share3 | |||
</pre> | </pre> | ||
* Reload your exports | * Reload your exports: | ||
<pre>su -c "/usr/sbin/exportfs -rv"</pre> | <pre>su -c "/usr/sbin/exportfs -rv"</pre> | ||
* Edit your <code>/etc/hosts.allow</code> file, so your clients are allowed to access your | * Edit your <code>/etc/hosts.allow</code> file, so your clients are allowed to access your shares: | ||
<pre>su -c "vim /etc/hosts.allow"</pre> | <pre>su -c "vim /etc/hosts.allow"</pre> | ||
* Allow your LAN to access your | * Allow your LAN to access your shares: | ||
<pre>rpcbind: 192.168.1.0/255.255.255.0</pre> | <pre>rpcbind: 192.168.1.0/255.255.255.0</pre> | ||
=== Configuring the clients === | === Configuring the clients === | ||
Revision as of 07:48, 8 November 2013
Sharing files with NFSv4 on Fedora (Server & Client configuration)
Description
This HowTo explains how to set up the Network File System version 4 on your LAN for multiple shares. It explains, also, how to mount the exports on your client.
Tested in Fedora Versions
- Fedora 19
Requirements
The nfs-utils package provides what's need for both then client and the server. However, to make sure it's installed, run the following command. Enter your root password when prompted:
su -c "yum install nfs-utils"
Server requirements (services)
rpcbindrpcidmapdnfslocknfs
Client requirements ((services)
rpcbindrpcidmapdnfslocknfs
Doing the Work
Configuring the server
- Change your eth1 (internal) interface to the "internal" zone
su -c 'firewall-cmd --zone=internal --change-interface=eth1'
- Open up the necessary port on the firewall (
port: 2049 TCP).
su -c "firewall-cmd --permanent --zone=internal --permanent --add-service=nfs" su -c "firewall-cmd --reload"
- Edit
/etc/idmapd.conf. Enter yourrootpassword when prompted:
su -c "vim /etc/idmapd.conf"
- Configure your domain name and change the users to
nfsnobody:
[General] Domain = domain.tld [Mapping] Nobody-User = nfsnobody Nobody-Group = nfsnobody
- Enable
rpcbind,rpcidmapd,nfslock, andnfsservices to start at boot:
su -c "systemctl enable rpcbind.service rpcidmapd.service nfslock.service nfs.service"
- Start those services:
su -c "systemctl start rpcbind.service rpcidmapd.service nfslock.service nfs.service"
- Edit
/etc/exports. Enter yourrootpassword when prompted:
su -c "vim /etc/exports"
- Add your shares here (available to your home network) If you want your shares to be read only, change
rwtorofrom these statements:
/srv/nfs/share1 192.168.1.0/255.255.255.0(rw,async) /srv/nfs/share2 192.168.1.0/255.255.255.0(ro) /srv/nfs/share3 192.168.1.0/255.255.255.0(rw)
- Reload your exports:
su -c "/usr/sbin/exportfs -rv"
- Edit your
/etc/hosts.allowfile, so your clients are allowed to access your shares:
su -c "vim /etc/hosts.allow"
- Allow your LAN to access your shares:
rpcbind: 192.168.1.0/255.255.255.0
Configuring the clients
- Edit
/etc/idmapd.conf. Enter yourrootpassword when prompted:
su -c "vim /etc/idmapd.conf"
- Configure your domain name and change the users to
nfsnobody:
[General] Domain = example.com [Mapping] Nobody-User = nfsnobody Nobody-Group = nfsnobody
- Edit
/etc/fstab. Please enter yourrootpassword when prompted:
su -c "vim /etc/fstab"
- Create the mounting directories:
su -c "mkdir /mnt/shares /home/me/share1 /home/he/share2 /home/it/share3"
- Add the desired shares:
<ip-address-to-server>:/ /mnt/shares nfs4 rsize=8192,wsize=8192,timeo=14,soft <ip-address-to-server>:/share1 /home/me/share1 nfs4 rsize=8192,wsize=8192,timeo=14,soft <ip-address-to-server>:/share2 /home/he/share2 nfs4 rsize=8192,wsize=8192,timeo=14,soft <ip-address-to-server>:/share3 /home/it/share3 nfs4 rsize=8192,wsize=8192,timeo=14,soft
- Remount everything:
su -c "mount -a"
Common problems and fixes
Exported subdirectory appears empty
If /srv/nfs/share1 appears empty on the client make sure it's exported with the nohide parameter. Because /srv/nfs/share1 was mounted under /srv/nfs, the client can't see it unless the nohide parameter is used.
More Information
RedHat recommends, on RHEL5 Docs, that one should use automount instead of /etc/fstab; which saves resources when sharing to multiple workstations. I haven't had the time to try this configuration. This document will be modified/augmented once I've got the hang of it.
Disclaimer
I haven't had the opportunity to test this HowTo since I lack of a networked PC to do it, so you may run into problems, if you do, come to #fedora on irc.freenode.net or leave me messages so I know what's up. Feel free to propose changes and stuff.