Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
exportfs -ra was then run and nfs already starts at boot.
On the client side I ran the following command:
mount 192.168.0.3:/mnt/share /nfs
^(the IP of the server)
When I cd to the /nfs I get the two directories, music and video (which is correct), but changing into these directories shows nothing.
Both have the 2.4.19 kernel on them. The LAN is setup on a machine running 2.2.22 kernel and ipchains.
I am not sure of a few things:
1 - Are there any special services I have to start at boot for this?
2 - Do I have this code setup correctly?
3 - Do I have to enable any new rules for IPChains?
4 - Any special options for the kernel?
5 - Any thing else you can think of?
Distribution: Redhat v8.0 (soon to be Fedora? or maybe I will just go back to Slackware)
Posts: 857
Rep:
On the server... what does "ls -l /mnt/" show the permissions of "share" as? How about the directorys inside of "share"?
On the client, after mounting, what does "ls -l /" show the permisions of "nfs" as?
... "ls -l /nfs" ?
... "ls -l /nfs/music"? (just show for any one file)
... "ls -l /nfs/video"? (just show for any one file)
are you sharing a native file system, or something such as fat32? NFS won't touch fat32 due to it's total lack of file ownership and other such handy and secure things.
Root has no permissions for security reasons
If you need to do this:
on the server
/mnt/share 192.168.0.2(rw,no root squash)
But I would ssh to the server for root. NFS, like samba is a method to share ordinary user files. Do you really want to make the entire root file system avaible to a client machine?
I believe each partion has to be a differnet share.
I'm a little rusty on this but if your server mount point is /mnt/share then exports should be
/share 192.168.0.2(rw) NOT /mnt/share
On the client you created a directory under /mnt called nfs and you would then mount 192.168.0.3:/share /mnt/nfs
The client you're logging attaching from obviously needs rights to these directories, to cover all bases temporarily set the permisions to 777 so anyone can see the files, if it works you can change the right back to whatever you want.
Great, if /mnt/share is the actual partition name then that would be correct. If not maybe it's a version thing, I'm using RH7.2 and I export home directories as /home
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.