From: Louie <snikrep@gmail.com>
To: David Brodbeck <brodbd@uw.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: v4recovery client id lockup
Date: Fri, 24 Feb 2012 16:32:12 -0800 [thread overview]
Message-ID: <CAMgFM3BT104oF5p2FDMK7ofrnLESUSVAsWnsk4iweF5L61SLrQ@mail.gmail.com> (raw)
In-Reply-To: <CAHHaOuasyyQY7p+HCRwyYuJDT0mmmXUpUCivfp9D8nNRUQ9qDg@mail.gmail.com>
Good idea, went ahead and implemented this, and everything appears to
be working.
Sure glad to solve this, was driving us absolutely nuts (it would
freeze the NFS connections to our lab computers, which would crash
everything).
Many thanks!!
-Louie
On Fri, Feb 24, 2012 at 2:29 PM, David Brodbeck <brodbd@uw.edu> wrote:
>
>
> On Fri, Feb 24, 2012 at 1:08 PM, Louie <snikrep@gmail.com> wrote:
>>
>> I'm guessing there is no solution and our setup just isn't supported.
>> I'm leaning towards ditching the SSH tunnels and going with
>> unencrypted traffic for now, as it's not strictly necessary. But if
>> anybody has a tip on how to fix, would love to hear.
>>
>
> You could always switch to a VPN solution of some kind, such as OpenVPN.
> This would let your clients have different IPs while still preserving the
> security advantages of an SSH tunnel.
>
> --
> David Brodbeck
> System Administrator, Linguistics
> University of Washington
>
next prev parent reply other threads:[~2012-02-25 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 1:06 v4recovery client id lockup Louie
2012-02-23 16:52 ` Jeff Layton
2012-02-24 21:08 ` Louie
[not found] ` <CAHHaOuasyyQY7p+HCRwyYuJDT0mmmXUpUCivfp9D8nNRUQ9qDg@mail.gmail.com>
2012-02-25 0:32 ` Louie [this message]
2012-02-28 19:45 ` J. Bruce Fields
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=CAMgFM3BT104oF5p2FDMK7ofrnLESUSVAsWnsk4iweF5L61SLrQ@mail.gmail.com \
--to=snikrep@gmail.com \
--cc=brodbd@uw.edu \
--cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).