Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I have gone back and implemented your suggestions, which I
was in the process of doing earlier.
However, when I attempt to mount the server directory on
the client, I get an error.
e.g. if I type
mount -t nfs svr_name:/svr_directory /client_dir
mount: svr_name:svr_directory failed, reason given by server: Permission denied.
The /etc/exports file on the server lists the svr_directory
with read-only access by IP address, e.g.
rpc.mount and nfsd show in a px aux list.
I still think my problem is that the kernel on the client and the server do not list nfs in cat /proc/filesystems.
Both the O'Reilly Network Admin Guide and the NFS HOWTO state
that the kernel needs nfs support and use the
cat /proc/filesystems command for determining if it is there.
Also, on both machines, ipchains -L shows
Chain input (policy ACCEPT):
Chain forward (policy ACCEPT):
Chain output (policy ACCEPT):
I have read that firewalling sometimes interferes with nfs
so I opened it up.
I have also run exportfs -a -v on the server and it
acknowledges reexporting the directories to the kernel.
I guess what puzzles me is why it would say that if the
cat /proc/filesystems does not list nfs.
I put a bunch of "echo .... " > /tmp/nfs-start.out
statements in the nfs startup file.
Uses /etc/rc.d/init.d/nfs in RH.
Apparently the client also wants an /etc/exports file.
I thought the server needed the /etc/exports file to see
which directories it could export when someone did a
mount -t nfs server:/nfsdir
from the client. What is the client doing with it?
I'm not sure what the client is using /etc/exports for in
this case since all it has in it (on the client) is
service start nfs
will fail if /etc/exports is not there.
It also has to be > 0 bytes.
Right now I have two machines with an nfs directory
mounted from the other (not the same ones) and all
seems to be OK.
Thanks for your help. I have about 10 years of Unix,
(and not much networking) but only 6 months of Linux so
a lot of this is new. Now on to NIS.
The client doesn't need to run any nfsd processes, just the server. The reason you are having to create a /etc/exports file is because you are starting up an nfs server on the client... the server looks for /etc/exports.
I can't remember what daemons the client needs other than portmap... even rpc.mountd is only needed by the server.