UbuntuHelp:SettingUpNFSHowTo

文章出处:

https://help.ubuntu.com/community/SettingUpNFSHowTo

点击翻译:

English

NFS Server

Pre-Installation Setup

User Permissions

NFS user permissions are based on user ID (UID). UIDs of any users on the client must match those on the server in order for the users to have access. The typical ways of doing this are:

• Manual password file synchronization
• Use of LDAP
• Use of NIS

It's also important to note that you have to be careful on systems where the main user has root access - that user can change UID's on the system to allow themselved access to anyone's files. This page assumes that the administrative team is the only group with root access and that they are all trusted. Anything else represents a more advanced configuration, and will not be addressed here.

Group Permissions

With NFS, a user's access to files is determined by his/her membership of groups on the client, not on the server. However, there is an important limitation: a maximum of 16 groups are passed from the client to the server, and, if a user is member of more than 16 groups on the client, some files or directories might be unexpectedly inaccessible.

Host Names

~- optional if using DNS -~

Add any client name and IP addresses to /etc/hosts. The real (not 127.0.0.1) IP address of the server should already be here. This ensures that NFS will still work even if DNS goes down. You could rely on DNS if you wanted, it's up to you.

NIS

~- optional - perform steps only if using NIS -~

Note: Ths only works if using NIS. Otherwise, you can't use netgroups, and should specify individual IP's or hostnames in /etc/exports. Read the BUGS section in man netgroup.

Edit /etc/netgroup and add a line to classify your clients. (This step is not necessary, but is for convenience).

myclients (client1<sub>) (client2</sub>)
</code>
Obviously, more clients can be added. <code>myclients</code> can be anything
you like; this is a ''netgroup name''.

Run this command to rebuild the YP database:
<pre>
sudo make -C /var/yp
</code>

===== Portmap Lockdown =====
~- optional -~

Add the following line to /etc/hosts.deny:
<pre>
portmap mountd nfsd statd lockd rquotad : ALL
</code>
By blocking all clients first, only clients in /etc/hosts.allow below will be allowed to access the server.

Now add the following line to /etc/hosts.allow:
<pre>
portmap mountd nfsd statd lockd rquotad : list of IP addresses
</code>
Where the "list of IP addresses" string is, you need to make a list
of IP addresses that consists of the server and all clients. These have
to be IP addresses because of a limitation in portmap (it doesn't like
hostnames). Note that if you have NIS set up, just add these to the
same line.

==== Installation and Configuration ====

===== Install NFS Server =====

<pre>
sudo apt-get install portmap nfs-kernel-server
</code>

===== Shares =====

Edit /etc/exports and add the shares:
<pre>
/home @myclients(rw,sync)
/usr/local @myclients(rw,sync)
</code>

The above shares /home and /usr/local to all clients in the
myclients netgroup.

<pre>
/home 192.168.0.10(rw,sync) 192.168.0.11(rw,sync)
/usr/local 192.168.0.0/255.255.255.0(rw,sync)
</code>

The above shares /home and /usr/local to two clients with fixed ip addresses.
Best used only with machines that have static ip addresses.

<pre>
/home 192.168.0.0/255.255.255.0(rw,sync)
/usr/local 192.168.0.0/255.255.255.0(rw,sync)
</code>

The above shares /home and /usr/local to all clients in the
private network falling within the designated ip address range.

<code>rw</code> makes the share read/write, and <code>sync</code> requires
the server to only reply to requests once any changes have been flushed
to disk. This is the safest option (<code>async</code> is faster, but
dangerous. It is strongly recommended that you read <code>man exports</code>.

After setting up /etc/exports, export the shares:
<pre>
sudo exportfs -ra
</code>

You'll want to do this command whenever <code>/etc/exports</code> is modified.

===== Restart Services =====

If /etc/default/portmap was changed, portmap will need to be restarted: 
<pre>
sudo /etc/init.d/portmap restart
</code>

The NFS kernel server will also require a restart: 
<pre>
sudo /etc/init.d/nfs-kernel-server restart
</code>

==== Security Note ====

Aside from the UID issues discussed above, it should be noted that an
attacker could potentially masquerade as a machine that is allowed to
map the share, which allows them to create arbitrary UIDs to access
your files. One potential solution to this is [[UbuntuHelp:IPSecHowTo|IPSec]], see also the NFS and IPSec section below. You can set up all your domain members to talk only to each other over IPSec, which will effectively authenticate that your client is who it says it is.

IPSec works by encrypting traffic to the server with the server's key,
and the server sends back all replies encrypted with the client's key.
The traffic is decrypted with the respective keys. If the client doesn't have the keys that the client is supposed to have, it can't send or receive data.

An alternative to IPSec is physically separate networks. This requires a separate network switch and separate ethernet cards, and physical security of that network.

=== NFS Client ===

==== Installation ====

<pre>
sudo apt-get install portmap nfs-common
</code>

===== Portmap Lockdown =====

~- optional -~

Add the following line to /etc/hosts.deny:
<pre>
portmap : ALL
</code>
By blocking all clients first, only clients in /etc/hosts.allow below will be allowed to access the server.

Now add the following line to /etc/hosts.allow:
<pre>
portmap : NFS server IP address
</code>
Where "NFS server IP address" is the IP address of the server. '''This must be numeric!''' It's the way portmap works.

===== Host Names =====

~- optional if using DNS -~

Add the server name to /etc/hosts.  This ensures the NFS mounts will still work even if
DNS goes down. You could rely on DNS if you wanted, it's up to you.

==== Mounts ====


===== Check to see if everything works =====

You should try and mount it now. The basic template you will use is:
<pre>
sudo mount ServerIP:/folder/already/setup/to/be/shared /home/username/folder/in/your/local/computer
</code>

so for example:

<pre>
sudo mount 192.168.1.42:/home/music /home/poningru/music
</code>

===== Mount at startup =====

NFS mounts can either be automatically mounted when accessed using autofs or can be setup with static mounts using entries in /etc/fstab.

===== Automounter =====

Install autofs:
<pre>
sudo apt-get install autofs
</code>

The following configuration example sets up home directories to automount off an NFS server upon logging in.  Other directories can be setup to automount upon access as well.

Add the following line to the end of /etc/auto.master:
<pre>
  /home         /etc/auto.home
</code>

Now create /etc/auto.home and insert the following:
<pre>
**             solarisbox1.company.com.au,solarisbox2.company.com.au:/export/home/&
</code>
The above line automatically mounts any directory accessed at /home/[username] on the client machine from either solarisbox1.company.com.au:/export/home/[username] or solarisbox2.company.com.au:/export/home/[username].

Restart autofs to enable the configuration:
<pre>
sudo /etc/init.d/autofs start
</code>

===== Static Mounts =====

Prior to setting up the mounts, make sure the directories that will act as mountpoints are already created.

In /etc/fstab, add lines for shares such as:
<pre>
servername:dir /mntpoint nfs rw,hard,intr 0 0
</code>
The <code>rw</code> mounts it read/write. Obviously, if the server is sharing
it read only,
the client won't be able to mount it as anything more than that. The
<code>hard</code> mounts the share such that if the server becomes
unavailable, the program will wait until it is available. The
alternative is <code>soft</code>. <code>intr</code> allows you to interrupt/kill the
process. Otherwise, it will ignore you. Documentation for these can be
found in the <code>Mount options for nfs</code> section of <code>man mount</code>.

The filesystems can now be mounted with <code>mount /mountpoint</code>, or <code>mount -a</code> to mount everything that should be mounted at boot.

=== IPSec Notes ===

If you're using IPSec, the default shutdown order in Breezy/Dapper causes the client to hang as it's being shut down because IPSec goes down before NFS does. To fix it, do:

<pre>
sudo update-rc.d -f setkey remove
sudo update-rc.d setkey start 37 0 6 S .
</code>

A bug has been filed here:
https://launchpad.net/distros/ubuntu/+source/ipsec-tools/+bug/37536

=== Credits ===

* MatthewCaron - NFS Server, NFS Client, IPSec Notes
* NaamanCampbell - NFS Client - Automount

----
CategoryDocumentation

[[category:UbuntuHelp]]