Linux NFS development
 help / color / mirror / Atom feed
From: Le Rouzic <aime.le-rouzic@bull.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	trond.myklebust@netapp.com, trond.myklebust@fys.uio.no,
	linux-nfs@vger.kernel.org, Frank S Filz <ffilz@us.ibm.com>
Subject: Re: [PATCH 3/8] SUNRPC: Set V6ONLY socket option for RPC listener sockets
Date: Thu, 21 Aug 2008 17:32:02 +0200	[thread overview]
Message-ID: <48AD8A72.2040200@bull.net> (raw)
In-Reply-To: <20080821144117.GB22587@fieldses.org>

J. Bruce Fields a =C3=A9crit :

>>J. Bruce Fields a =C3=A9crit :
>>   =20
>>
>>>>>so suppose I'm a server
>>>>>administrator, and want my nfs server to listen for ipv6 connectio=
ns.
>>>>>Will there be some switch I'll need to flip?
>>>>>         =20
>>>>>
>
> =20
>
>>>On Thu, Aug 14, 2008 at 04:45:31PM -0400, Chuck Lever wrote:
>>>     =20
>>>
>>>>I don't know how that UI will be designed.  So far, I've focused on=
ly=20
>>>>on the pieces needed for client side IPv6 support.  I figured the=20
>>>>Bull team had something figured out for the server, and didn't thin=
k=20
>>>>any more about it.
>>>>       =20
>>>>
>>>I've forgotten who was working on that; Aurelien Charbon?
>>>     =20
>>>
>
>On Thu, Aug 21, 2008 at 02:11:49PM +0200, Le Rouzic wrote:
> =20
>
>>Sorry for not answering before, I am back from vacation.  Aurelien is
>>no longer directly working on that even he can answer any  questions.
>>It is me now who tess NFSV4 IPV6 with the patches Aurelien delivered
>>to Bruce a few months ago.  But since Chuck has delivered several new
>>patches which affect the NFS server side about the way nfsd can liste=
n
>>for ipv6 connections.
>>   =20
>>
>
>I merged the last patch I can remember from Aurelien (f15364bd "IPv6
>support for NFS server export caches").  Are there some others floatin=
g
>around that I should look at?
>
> =20
>
>> To have NFSV4 IPV6 working with those changes, what it would be nice
>> to have a complete list on what are the changes.  Is there now a
>> complete release for which we can test those latest  changes? If not
>> which one will be?  Are there any other changes still planned?
>>   =20
>>
>
>I was hoping you or Chuck would know; I don't know of anyone else
>working on nfs over ipv6.
> =20
>
   Hi,
About changes I was talking about changes introduced for IPv6 RPC=20
services via rpcbind
at least thoses published on the 19th on this mailing list can be=20
considered like the last
ones.

Cheers

>--b.
>--
>To unsubscribe from this list: send the line "unsubscribe linux-nfs" i=
n
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
> =20
>


--=20
-----------------------------------------------------------------
Company : Bull, Architect of an Open World TM (www.bull.com)
Name    : Aime Le Rouzic=20
Mail    : Bull - BP 208 - 38432 Echirolles Cedex - France
E-Mail  : aime.le-rouzic@bull.net
Phone   : 33 (4) 76.29.75.51
=46ax     : 33 (4) 76.29.75.18
-----------------------------------------------------------------=20


  reply	other threads:[~2008-08-21 15:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 22:39 [PATCH 0/8] Support rpcbind v4 in kernel's RPC server Chuck Lever
     [not found] ` <20080813223653.13068.9467.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-08-13 22:39   ` [PATCH 1/8] NFS: nfs_parsed_mount_options can use unsigned int Chuck Lever
     [not found]     ` <20080813223937.13068.47032.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-23 19:42       ` Trond Myklebust
2008-08-13 22:39   ` [PATCH 2/8] SUNRPC: Add address family field to svc_serv data structure Chuck Lever
2008-08-13 22:39   ` [PATCH 3/8] SUNRPC: Set V6ONLY socket option for RPC listener sockets Chuck Lever
     [not found]     ` <20080813223953.13068.97829.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-08-14 20:05       ` J. Bruce Fields
2008-08-14 20:34         ` Chuck Lever
2008-08-14 20:38           ` J. Bruce Fields
2008-08-14 20:45             ` Chuck Lever
2008-08-20 19:31               ` J. Bruce Fields
2008-08-21 12:11                 ` Le Rouzic
2008-08-21 14:41                   ` J. Bruce Fields
2008-08-21 15:32                     ` Le Rouzic [this message]
2008-08-21 16:20                       ` Chuck Lever
     [not found]                         ` <76bd70e30808210920y3db1b07cyccbe40e1b4582c12-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-21 21:26                           ` J. Bruce Fields
2008-08-13 22:40   ` [PATCH 4/8] SUNRPC: Use proper INADDR_ANY when setting up RPC services on IPv6 Chuck Lever
2008-08-13 22:40   ` [PATCH 5/8] SUNRPC: Split portmap unregister API into separate function Chuck Lever
2008-08-13 22:40   ` [PATCH 6/8] SUNRPC: Refactor svc_register() Chuck Lever
     [not found]     ` <20080813224016.13068.29786.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-08-14 20:36       ` J. Bruce Fields
2008-08-14 21:11         ` Chuck Lever
2008-08-13 22:40   ` [PATCH 7/8] SUNRPC: Use new rpcb_v4_register() interface in svc_register() Chuck Lever
2008-08-13 22:40   ` [PATCH 8/8] SUNRPC: Add kernel build option to disable server-side use of rpcbind v3/v4 Chuck Lever

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=48AD8A72.2040200@bull.net \
    --to=aime.le-rouzic@bull.net \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=ffilz@us.ibm.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    --cc=trond.myklebust@netapp.com \
    /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