All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Suresh Jayaraman <sjayaraman@suse.de>, linux-nfs@vger.kernel.org
Subject: Re: NFS and mobile clients - can it work?
Date: Thu, 25 Sep 2008 14:13:44 +1000	[thread overview]
Message-ID: <18651.4088.147169.7967@notabene.brown> (raw)
In-Reply-To: message from Ric Wheeler on Wednesday September 24

On Wednesday September 24, rwheeler@redhat.com wrote:
> Suresh Jayaraman wrote:
> > Neil Brown wrote:
> >   
> >>  Suppose I have a mobile client such as a notebook computer which
> >>  changes networks from time to time - e.g. when "docked" it uses a
> >>  wired network, but when I "undock" it uses a wireless network.  And
> >>  as I move around it might change from one wireless network to
> >>  another.
> >>     
> >
> > This is quite a common scenario these days.
> >
> >   
> >>  Is it at all reasonable to expect that I could have an NFS mounted
> >>  filesystem that continues to work across all of those changes?
> >>     
> >
> > I think it is reasonable to expect with the changing network paradigm of
> > mobile computing. Successful protocols/implementations always have
> > adapted themselves to the changing (network) needs :)
> >   
> 
> The other place to address this is in the networking layer itself. If I 
> remember correctly, there is support in IPV6 for "mobile IP" which might 
> allow you to do this:
> 
> http://www.ietf.org/rfc/rfc2002.txt
> 
> I have no idea how much of this made it into working systems,
> 

You can get the same effect of a mobile IP with IPv4 using a VPN, such
as OpenVPN.

I think I've come to the conclusion that this is the only way to
reliably have a mobile NFS mount.  The server really has too much
investment in the IP of the client, both for locking and for the reply
cache.  Because of these, the Linux NFS client tries hard to reconnect
from the same source address when it does reconnect, and this is
unlikely to change (I suspect).

When a client does change IP address, all NFS mounts should be
unmounted (probably umount --lazy) and an automounter should be used
to re-establish them on demand.

It is conceivable that the connection could be broken and
re-established without requiring the re-mount.  But as it would have
to drop all locks and lose any benefits of the server's reply cache,
it should not happen automatically.

If you want really mobile mounts, use OpenVPN or similar.

Thanks everyone for your input.

NeilBrown

  reply	other threads:[~2008-09-25  4:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22  0:20 NFS and mobile clients - can it work? Neil Brown
     [not found] ` <18646.58594.377630.950531-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-09-22  5:30   ` Krishna Kumar2
2008-09-24  7:19   ` Suresh Jayaraman
2008-09-24 13:26     ` Ric Wheeler
2008-09-25  4:13       ` Neil Brown [this message]
2008-09-24 15:24   ` Steve Dickson
     [not found]     ` <48DA5B93.5030307-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-09-24 15:52       ` Jim Rees

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=18651.4088.147169.7967@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rwheeler@redhat.com \
    --cc=sjayaraman@suse.de \
    /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.