Skip to main content

How to configure Network file system (NFS) client?

68.How to configure Network file system (NFS) client?
Ans.
1. To configure client, make sure that the portmapper, NFS file locking daemons statd & lockd, mount command are avaialbe.

2. NFS client needs the portmapper running in order to process and route RPC calls and returns from the server to the appropriate port and programs.

3. We can ensure portmapper is running or not by using following command:
#service portmap status

4. If portmapper is not running then it’ll show us portmapper is stopped to start portmapper we’ll use following command:
#service portmap start

5. Mounting can be done using following commands:
For example we wants to mount /media from the server configured at the end then we’ll execute following commands:
#mount –t nfs 192.168.166.5:/media /media

6. If user wish, he/she can specify client mount options using mounts arguments as;
#mount –t nfs 192.168.166.5:/media /media -o resize=8292,wsize=8192, hard, nolock

7. Following are the mounting options:
bg – Enables mount request to run in the background if first fails
fg – Enables mount request to run in the foreground if first fails
hard – Enables client to continue retrying if server does not respond
soft – Enables client operation to fail and terminate
tcp – Declares protocol to be tcp
udp – Declares protocols to be udp
resize=n – Declares read size of clients buffer
wsize=n – Declares write size of clients buffer
retry=n – Enables n retries for mounting
intr – Enables ctrl+c to work as interrupt
lock – Starts nfs locking via statd and lockd
nfsvers=n – Specifies versions of nfs
port=n – specifies nfs server port for connection

Comments

Popular posts from this blog

Java,ES,QT practical files

All practical files: Click below to start download Uploaded on special request||||

Vidyalankar Question paper solutions

Download from their website: http://www.vidyalankar.org/index.aspx or just click here to download

Discuss security issues in Network File system.

71.Discuss security issues in Network File system. Ans. 1. NFS protocol version 3 and older have some security problems that make it unsuitable for use across the Internet and potentially unsafe for use even in trusted network. 2. One NFS weakness, in general terms, is the /etc/exports file, if a cracker is able to spoof or take over a trusted address, an address listed in /etc/exports then your exported NFS mount are accessible. 3. NFS has normal Linux file system access controls that take over once a client has mounted an NFS export, once this happens normal user and group permissions on the files take over access control. 4. The 1st way to defense is to use host access control, to limit access to services , particularly the portmapper, which has long been target of exploits attempts. 5. For this add the entries in /etc/hosts.clevy lockd, statd, mountd and rquoted. 6. Careful use of IS packet firewall, using netfilter, dramatically increases NFS server security. ...