Skip to main content

Setting up NFS v4.0 in RHEL/CentOS 6.x

After you've installed NFS v4.0 and its required dependencies in your CentOS server, there are only seven steps to configure it.

Server Instructions
1. Edit the file "/etc/exports" that's the access control list for serving directories of file systems to NFS clients:
/<directory>  <hostname or fqdn>(options) ...
/<directory>  <ip address>/<prefix length>(options) ... 

2. Change the default runlevels for the services used by your NFS server:
chkconfig --levels 35 nfs on;
chkconfig --levels 35 portmap on;

3. Automatically start each service on boot up:
update-rc.d portmap <options>;
update-rc.d nfs <options>;

4. Start each service used by your NFS server:
service portmap start;
service nfs start;

5. Edit the file "/etc/hosts.allow" that's the hosts access control list for allowing access to services on your server from specific hostnames, IP addresses, networks, and FQDNs:
<service or wildcard>: <hostname> <ip address>/<subnet mask> <fqdn>

6. Edit the file "/etc/hosts.deny" that's the hosts access control list for denying access to services on your server from specific hostnames, IP addresses, networks, and FQDNs:
<service or wildcard>: <hostname> <ip address>/<subnet mask> <fqdn>

7. Allow incoming and outgoing client connections to your NFS server through your firewall:
iptables -A INPUT -i <interface> -p tcp --dport 2049 -j ACCEPT
iptables -A OUTPUT -o <interface> -p tcp --sport 2049 -j ACCEPT

Try connecting to the remote NFS share you set up.

Client Instructions
1. Edit the file "/etc/fstab" that automatically mounts partitions, file systems, and NFS shares:
<server>:/  /<directory>  nfs4  <option>=<value>,<option>=<value>,...

2. Allow outgoing client connections to your NFS server through your firewall:
iptables -A INPUT -i <interface> -p tcp --sport 2049 -j ACCEPT
iptables -A OUTPUT -o <interface> -p tcp --dport 2049 -j ACCEPT

Do you have a suggestion about how to improve this blog? Let's talk about it. Contact me at David.Brenner.Jr@Gmail.com or 720-584-5229.

Comments

Post a Comment

Comments to this blog will be reviewed within 72 hours. No trolling please

Popular posts from this blog

The meaning of time in reinforcement learning

Reinforcement learning (RL) is one of three basic machine learning paradigms, alongside supervised learning and unsupervised learning. Reinforcement learning is concerned with how software agents ought to take actions in an environment in order to maximize the notion of cumulative reward through the process of trial and error. In reinforcement learning an agent starts at an empty state then analyzes the available datasets according to a policy of positive states and negative states. Rather than being explicitly taught as in supervised learning the correct set of actions for performing a task, reinforcement learning uses rewards as signals for positive states and punishments as signals for negative states. The agent obtains the best path to a desirable reward as a cumulation of positive states and negative states. As compared to unsupervised learning, reinforcement learning is different in terms of goals. While the goal in unsupervised learning is to find similarities and differences...
Post a Comment
Read more

Threat detection of zero-day attacks in Linux with Python

You can investigate suspicious activity that could be a zero-day attack by collecting relevant machine data from your endpoint. You can use the machine data to create your own analysis. Before you start your investigation you will need to determine normal activity on your endpoint. Normal activity is the scope of functionality of the software on your endpoint during periods of low activity and high activity. You will need some kind of software that periodically collects specific machine data from your endpoint like my software developed in Python that's available for free download at https://github.com/davidbrennerjr/server-stats-collector Ingest one or more of the following machine data: General system-wide error messages from /var/log/syslog Auditing logs of application rulesets Auditing logs of security contexts Auditing logs of login attempts from /var/log/auth.log Auditing logs of user management or group manageme...
Post a Comment
Read more

Web app comparison of async and real-time

Advantages of asynchronous web apps Generic request/response structure Stateless session control Message queue management Token access based on serverside date-time format PostgreSQL paging using token-centric tables and functions Shared pools of resources per customer One-to-many security policies Single domain name with TLS cert over HTTPS Shared bandwidth for uploads/downloads No endpoint/device registration No direct access to server resources Web app aggregation as control panel A/B Testing Advantages of (near) real-time web apps Stateful session control On-demand communication protocols per customer Custom request/response structure per customer Custom date-time formats per customer Endpoint/device registration PostgreSQL paging using static tables and aggregate functions Immediate execution of requests Dedicated pools of resources per customer Dedicated TLS cert over HTTPS per customer Dedicated IP addres...
Post a Comment
Read more