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.
Here is the error message when I restart the nfsserver:
Vidious:/home/dabeast # /etc/init.d/nfsserver restart
Shutting down kernel based NFS server done
Starting kernel based NFS serverexportfs: No options for /home/dabeast 192.168.3.0/28: suggest 192.168.3.0/28(sync) to avoid warning
exportfs: No host name given with /home/dabeast (rw,async,no_root_squash), suggest *(rw,async,no_root_squash) to avoid warning done
Your /etc/exports is only allowing access to 192.168.3.0/28, which is 192.168.3.1-192.168.3.14. You might want to change either the network or the mask. 192.168.0.0/16 would work, but is very broad. 192.168.4.0/24 is more specific, but excludes the .3.0 network.
or would I have to add 192.168.3.0/28 as well since the server is on that network? Also after I make any adjustments, do I just need to restart the nfsserver or the rest of the suite.?
Last edited by metallica1973; 07-26-2006 at 07:24 PM.
I chose a subnet mask of 255.255.255.240 as my subnet according to what my needs are and the ip of the client is 192.168.4.6 and the ip of the server is 192.168.3.1 which hosts the /home/dabeast and they are all of the same subnet of /28. I dont believe that is the issue or is it? Are you playing the jedi mind trick on me?
Last edited by metallica1973; 07-26-2006 at 08:24 PM.
It works. Here is a quick and simple how to for the idjiot out there myself:
1 - verify that you have these services running:
(SUSE 10)
nfsd
nfsboot
nfsserver
portmap
2 - edit the /etc/exports file and add an entry for the directory that you want shared, the ip address of the network or machine that you want to grant access for, and the permission of the share: an example
which means: share the home directory of dabeast to the 192.168.4.0/28 network and grant them read and write access and also allow root access. This is very dangerous but this is a very basic example.
3 - edit the hosts.allow and the hosts.deny with the proper entries. The hosts.allow is examined first and if nothing is found then entries from the hosts.deny is assumed.
http-rman : ALL EXCEPT LOCAL
portmap: ALL
lockd: ALL
mountd: ALL ## Denies Access for everything
rquotad: ALL
statd: ALL
4 - Finally, After all modification have been done then you must restart the service for the changes to take effect like /etc/init.d/nfsserver restart and /etc/init.d/portmap restart. Now check the mount with the showmount -e
Export list for MetalHead:
/home/dabeast 192.168.4.0/28
5 - Now you can attempt to mount from any workstation
with mount 192.168.3.1:/home/dabeast /mnt/caca
I hope this helps - Rock On
Last edited by metallica1973; 07-26-2006 at 09:30 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.