Linux - Networking This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
02-18-2014, 12:57 PM
|
#1
|
Member
Registered: Apr 2011
Location: Galiano Island, BC
Distribution: Linux Mint
Posts: 76
Rep:
|
My NSF setup good? bad? Please?
How does my /etc/exports file look? Any Problems?
How about my /etc/hosts.allow ?
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/export 192.168.1.0/24(rw,fsid=0,insecure,no_subtree_check,async)
/export/users 192.168.1.0/24(rw,nohide,insecure,no_subtree_check,async)
/var/nfs * (ro,async,subtree_check)
/var/nfs 192.168.1.1/24 (ro,async,subtree_check)
/home 192.168.0.104(rw,sync,no_root_squash,no_subtree_check)
/var/nfs 192.168.0.104(rw,sync,no_subtree_check)
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/export 192.168.1.0/24(rw,fsid=0,insecure,no_subtree_check,async)
/export/users 192.168.1.0/24(rw,nohide,insecure,no_subtree_check,async)
/var/nfs * (ro,async,subtree_check)
/var/nfs 192.168.1.1/24 (ro,async,subtree_check)
/home 192.168.0.104(rw,sync,no_root_squash,no_subtree_check)
/var/nfs 192.168.0.104(rw,sync,no_subtree_check)
|
|
|
02-19-2014, 07:58 AM
|
#2
|
Senior Member
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983
|
do you have any OSx users that will be connecting to the NFS share?
If not, then drop the insecure line, it will not be required for Linux users, its only required for OSx users as for some reason Apple is not keeping up to date with their NFS connection services. In fact OSx is still stuck in NFSv3 world they are so far behind.
|
|
|
02-19-2014, 11:07 AM
|
#3
|
Member
Registered: Apr 2011
Location: Galiano Island, BC
Distribution: Linux Mint
Posts: 76
Original Poster
Rep:
|
My NSF setup good? bad? Please?
Thanks Lieb, I have no OSx users, so which is the Mac users line??
I've just been following instructions from Ubuntu howtos. I'm not even sure how to use NFS when it is in place!
Quote:
Originally Posted by lleb
do you have any OSx users that will be connecting to the NFS share?
If not, then drop the insecure line, it will not be required for Linux users, its only required for OSx users as for some reason Apple is not keeping up to date with their NFS connection services. In fact OSx is still stuck in NFSv3 world they are so far behind.
|
|
|
|
02-19-2014, 09:32 PM
|
#4
|
Senior Member
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983
|
i told you. its the word insecure. that is used 99.99% of time only if you have OSx in your network accessing the shares.
here is my exports:
Code:
$ cat /etc/exports
#
# /etc/exports
# NFS4
/exports *(rw,insecure,subtree_check,crossmnt,fsid=0)
# NFSv3
/exports/centos/public *(rw,insecure,no_subtree_check,fsid=3010)
/exports/NFS_TV_Shows *(rw,insecure,no_subtree_check,fsid=3020)
few things to note.
1. i have the insecure as i have OSx in my network.
2. note that each and every export line has its own fsid. this is a good habit.
3. note i also support both NFSv3 and NSFv4, this again is due to having OSx in my network.
|
|
|
02-19-2014, 11:49 PM
|
#5
|
Member
Registered: Apr 2011
Location: Galiano Island, BC
Distribution: Linux Mint
Posts: 76
Original Poster
Rep:
|
Thank you Lieb! Sorry for my inattention. Here is/etc/hosts.allow in its new state;
# /etc/hosts.allow: list of hosts that are allowed to access the system.
# See the manual pages hosts_access(5) and hosts_options(5).
#
# Example: ALL: LOCAL @some_netgroup
# ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper, as well as for
# rpc.mountd (the NFS mount daemon). See portmap(8) and rpc.mountd(8)
# for further information.
#
rpcbind mountd nfsd statd lockd rquotad : 127.0.0.1 192.168.0.101 192.168.0.103 192.168.0.104 192.168.0.105 192.168.0.102
/export 192.168.1.0/24(rw,fsid=0,no_subtree_check,async)
/export/users 192.168.1.0/24(rw,nohide,no_subtree_check,async)
/var/nfs * (ro,async,subtree_check)
/var/nfs 192.168.1.1/24 (ro,async,subtree_check)
/home 192.168.0.104(rw,sync,no_root_squash,no_subtree_check)
/var/nfs 192.168.0.104(rw,sync,no_subtree_check)
cat /etc/exports
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/export 192.168.1.0/24(rw,fsid=0,no_subtree_check,async)
/export/users 192.168.1.0/24(rw,nohide,no_subtree_check,async)
/var/nfs * (ro,async,subtree_check)
/var/nfs 192.168.1.1/24 (ro,async,subtree_check)
/home 192.168.0.104(rw,sync,no_root_squash,no_subtree_check)
/var/nfs 192.168.0.104(rw,sync,no_subtree_check)
Last edited by hapibeli; 02-19-2014 at 11:58 PM.
Reason: adding info
|
|
|
02-20-2014, 01:01 PM
|
#6
|
Senior Member
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983
|
code flags are you friend, please use them. again you do not have fsid on each of your shares. id look into that if i were you.
|
|
|
All times are GMT -5. The time now is 06:31 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|