NFS /etc/exports question..
I've recently reclaimed a Gentoo server and turned it into a FreeBSD 6.2-RELEASE system (::sounds of cheering::). This is our file server, using NFS, and I had a question about /etc/exports: We have two subnets we export to--let's call them 127.0.1.0/255 and 10.0.5.0/255: # /etc/exports: NFS file systems being exported. See exports(5). /u2 -alldirs -maproot=root important1.domain.com important2.domain.com /u2/opt/portage -maproot=root -alldirs -network 127.0.0.0 -mask 255.255.255.0 /u2/opt/portage -maproot=root -alldirs -network 10.0.5.0 -mask 255.255.255.0 /u2 -alldirs -network 127.0.0.0 -mask 255.255.255.0 /u2 -alldirs -network 10.0.5.0 -mask 255.255.255.0 /usr -network 127.0.0.0 -mask 255.255.255.0 /usr -network 10.0.5.0 -mask 255.255.255.0 Now, this configuration does not work. I'm curious how to fix it--the logs say: Aug 21 12:29:33 nfsserver mountd[725]: can't change attributes for /u2 Aug 21 12:29:33 nfsserver mountd[725]: bad exports list line /u2 -alldirs -network 127.0.0.0 -mask 255.255.255.0 Aug 21 12:29:33 nfsserver mountd[725]: can't change attributes for /u2 Aug 21 12:29:33 nfsserver mountd[725]: bad exports list line /u2 -alldirs -network 10.0.5.0 -mask 255.255.255.0 One thing to note is that important1.domain.com and important2.domain.com are within the scope of 127.0.0.0/255. Granted, this wasn't an issue in Linux--I used to have machines listed by name (*.sub.olddomain.com), and had the exceptions listed with the no_root_squash parameter. So, basically.. what am I missing? :-/ Any help would be greatly appreciated. Google man 5 exports have not been my friends today :-/ Thanks in advance! Best, --Glenn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS /etc/exports question..
On Tuesday 21 August 2007 13:16:54 Glenn Sieb wrote: /u2 -alldirs... first up, that line negates the need for: /u2/opt/portage -alldirs alldirs, is all dirs! anything underneath is then redundant. /u2 -alldirs -maproot=root important1.domain.com important2.domain.com probably requires correctly configured DNS or proper entries in the hosts files. while you are working this problem out, i would eliminate that line, as it might be conflicting with: /u2 -alldirs -network 127.0.0.0 -mask 255.255.255.0 /u2 -alldirs -network 10.0.5.0 -mask 255.255.255.0 ... either of those lines. cheers, -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS /etc/exports question..
Hi Jonathan! Jonathan Horne wrote: On Tuesday 21 August 2007 13:16:54 Glenn Sieb wrote: /u2 -alldirs... first up, that line negates the need for: /u2/opt/portage -alldirs alldirs, is all dirs! anything underneath is then redundant. Understood. Fixed that. /u2 -alldirs -maproot=root important1.domain.com important2.domain.com probably requires correctly configured DNS or proper entries in the hosts files. while you are working this problem out, i would eliminate that line, as it might be conflicting with: /u2 -alldirs -network 127.0.0.0 -mask 255.255.255.0 /u2 -alldirs -network 10.0.5.0 -mask 255.255.255.0 Yes, because this was the question I had originally.. :) How can I make sure that I get -maproot=root on those two named boxes, which live inside the 127.0.0.0/255 network, while still allowing the rest of the boxes present in both other subnets to access the shared *without* -maproot=root? The errors I posted were specifically complaining about the 127.0.0.0 and 10.0.5.0 network lines (note, for security I am not posting the real network ranges). The two boxes in question, do have working DNS, and are boxes we use as our NIS masters, so I need to be able to create home directories on the fileserver, where the home directories live, hence needing maproot. The other boxes in the 127.0.0.0/255 range are other servers in my cluster, which need to mount directories from the fileserver--and in my case, a lot of users have sudo capability for testing/development purposes, so I don't want them having -maproot=root capability on those other servers. 10.0.5.0 is a range of IPs where my users mount their home directories and shared tools directories on their desktop boxes. Does this clear up my question? Thanks in advance! Best, --Glenn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS /etc/exports question..
On Tuesday 21 August 2007 14:44:29 Glenn Sieb wrote: Hi Jonathan! Jonathan Horne wrote: On Tuesday 21 August 2007 13:16:54 Glenn Sieb wrote: /u2 -alldirs... first up, that line negates the need for: /u2/opt/portage -alldirs alldirs, is all dirs! anything underneath is then redundant. Understood. Fixed that. /u2 -alldirs -maproot=root important1.domain.com important2.domain.com probably requires correctly configured DNS or proper entries in the hosts files. while you are working this problem out, i would eliminate that line, as it might be conflicting with: /u2 -alldirs -network 127.0.0.0 -mask 255.255.255.0 /u2 -alldirs -network 10.0.5.0 -mask 255.255.255.0 Yes, because this was the question I had originally.. :) How can I make sure that I get -maproot=root on those two named boxes, which live inside the 127.0.0.0/255 network, while still allowing the rest of the boxes present in both other subnets to access the shared *without* -maproot=root? The errors I posted were specifically complaining about the 127.0.0.0 and 10.0.5.0 network lines (note, for security I am not posting the real network ranges). The two boxes in question, do have working DNS, and are boxes we use as our NIS masters, so I need to be able to create home directories on the fileserver, where the home directories live, hence needing maproot. The other boxes in the 127.0.0.0/255 range are other servers in my cluster, which need to mount directories from the fileserver--and in my case, a lot of users have sudo capability for testing/development purposes, so I don't want them having -maproot=root capability on those other servers. 10.0.5.0 is a range of IPs where my users mount their home directories and shared tools directories on their desktop boxes. Does this clear up my question? Thanks in advance! Best, --Glenn then, probably eliminate just: /u2/opt/portage -maproot=root -alldirs -network 127.0.0.0 -mask 255.255.255.0 /u2/opt/portage -maproot=root -alldirs -network 10.0.5.0 -mask 255.255.255.0 and see what happens. -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS /etc/exports question..
Glenn Sieb wrote: I've recently reclaimed a Gentoo server and turned it into a FreeBSD 6.2-RELEASE system (::sounds of cheering::). This is our file server, using NFS, and I had a question about /etc/exports: snip Granted, this wasn't an issue in Linux--I used to have machines listed by name (*.sub.olddomain.com), and had the exceptions listed with the no_root_squash parameter. So, basically.. what am I missing? :-/ Any help would be greatly appreciated. Google man 5 exports have not been my friends today :-/ Thanks in advance! Best, --Glenn Hi Glenn, Have you checked for symlinks? NFS doesn't like symlinks for some reason. That held my /etc/exports up for a while. HtH, Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/etc/exports question
I'm trying to allow al machines in a 1/2 class C subnet to mount a given NFS mount point. I've put the following line in /etc/exports: /data maproot=root -network aaa.bbb.ccc.128 -mask 255.255.255.128 The NFS server is actually on network aaa.bbb.eee.0 netmask 255.244.255.128 But I get permission denied when I try to mount this filesystem from a machine on the aaa.bbb.ccc.128 netwokr. If I change the line in /etc/exports to: /data maproot=root hostname.example.com I can mount this filesystem. Is there an issue with the server not being directly on the target network? -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
