From: L A Walsh <lkml@tlinx.org>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: NFS subnet access problems
Date: Sat, 24 Jul 2004 13:00:41 -0700 [thread overview]
Message-ID: <4102BFE9.3070906@tlinx.org> (raw)
In-Reply-To: <40FF1FE7.4050403@tlinx.org>
Problem was had SuSE 9.0 manpages for 2.4 kernel loaded but had upgraded
to 2.6.
Getting new manpages from SuSE 9.1 solved my ignorance! :-)
Thanks to those who clued me in.
Blessings!
-linda
L A Walsh wrote:
> Jul 21 00:15:54 ishtar nfsd[1590]: Unauthorized access by NFS client
> 192.168.3.2.
> Jul 21 00:15:58 ishtar last message repeated 5928 times
>
> I wanted to give ro access to all clients on a 192.168.3.0/26 network
> to a "/Share"
> directory, and rw to a few, but I've never managed to get the network
> access
> statement to work correctly. Finally I switched to a /24 network to
> make netmasks more cleanI simply removed every thing but the
> 'ro' export of /Share which I thought should work but does not. The
> above
> client is an example.
>
> server:
> inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0
> /etc/exports:
> /Share 192.168.3.0/24(async,ro,no_subtree_check,nohide)
>
> > showmount -e
> Export list for server:
> /Share 192.168.3.0/24
>
> client:
> configed as inet addr:192.168.3.2 Bcast:192.168.3.255
> Mask:255.255.255.0
>
> Client had access when it was specifically given access by hostname,
> but doesn't
> solve access problems for anonymous dhcp hosts that I bring online as
> test machines.
>
> Are there some options needed for anon client access?
>
> the kernel seems to indicate it is exporting to the subnet, yet it is
> denying
> mount permisson...bug, misconfig?
>
> -linda
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2004-07-24 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 2:01 NFS subnet access problems L A Walsh
2004-07-24 20:00 ` L A Walsh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4102BFE9.3070906@tlinx.org \
--to=lkml@tlinx.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.