From: Chris Penney <cpenney@gmail.com>
To: nfs@lists.sourceforge.net
Subject: NAT & lockd
Date: Fri, 8 Apr 2005 09:25:08 -0400 [thread overview]
Message-ID: <111aefd050408062546161db8@mail.gmail.com> (raw)
I have an new NFS server (2.6.11.5 w/ NFS-ALL) that serves some
clients that sit behind a NAT box (linux clusters). It replaced a
SLES 8 file server. The NAT box is a old RH8 box (soone to be
upgraded to SLES 9). On the new NFS server I'm getting the following
messages from lockd:
nsm_mon_unmon: rpc failed, status=-13
lockd: cannot monitor x.x.x.x
With our old NFS server I never got any messages. The IP address
x.x.x.x is that of the NAT box. I'm curious if this means locking
does not work behind nat or if it means something else. Is there
anything I can do here? Would a 2.6.x based NAT box have a more up to
date iptables that supports lockd? This is non-critical, I'm just
trying to understand.
Chris
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-04-08 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 13:25 Chris Penney [this message]
2005-04-08 13:39 ` NAT & lockd Trond Myklebust
2005-04-08 14:08 ` Chris Penney
2005-04-08 15:12 ` Trond Myklebust
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=111aefd050408062546161db8@mail.gmail.com \
--to=cpenney@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=penney@msu.edu \
/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.