ipv6 status

ipv6 status

[Brian J. Murrell]

[-- Attachment #1: Type: text/plain, Size: 247 bytes --]

Hi All,

So what exactly is the status of NFS and IPv6 in the most recent (say,
2.6.24-28) kernels?  Is it present and if so, working?  Feel free to
simply point me to a roadmap that shows where we are if you like.

Cheers and thanx,
b.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: ipv6 status

[Chuck Lever]

On Nov 30, 2008, at Nov 30, 2008, 7:40 PM, Brian J. Murrell wrote:
> So what exactly is the status of NFS and IPv6 in the most recent (say,
> 2.6.24-28) kernels?  Is it present and if so, working?  Feel free to
> simply point me to a roadmap that shows where we are if you like.

There isn't a published roadmap.  Linux developers tend to eschew  
deadlines.

The NFS client in 2.6.28 (and maybe 2.6.27) should support NFSv4 over  
IPv6.  Use the latest nfs-utils.

I'm hoping 2.6.29 will see all the kernel pieces we need for NFSv2/v3  
client and server, and NFSv4 server support for IPv6.

Support for NFSv2/v3 over IPv6, and server-side support for NFSv4 over  
IPv6, requires user space changes.  We are pushing those into nfs- 
utils over time, but I don't expect that work to be complete until  
sometime in 1H2009.

-- 
Chuck Lever
chuck[dot]lever[at]oracle[dot]com

Re: ipv6 status

[Brian J. Murrell]

[-- Attachment #1: Type: text/plain, Size: 235 bytes --]

On Mon, 2008-12-01 at 13:33 -0500, Chuck Lever wrote:
> 
> There isn't a published roadmap.  Linux developers tend to eschew  
> deadlines.

Indeed.  :-)

Thanx for the update.  Looking forward to it finally finishing.

b.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

IPv6 Status

[Matthew Roy]

On 2009-10-02 there was a commit "use sockaddr_storage; and some ipv6
support groundwork" but I can't find any references to IPv6 support
being completed. Did that commit actually complete IPv6 support or are
more changes still required?

Commit diff:
http://ceph.newdream.net/git/p=ceph.git;a=commitdiff;h=dd732cbfc1c92f0d8dba2743a979baad6685a98c;hp=18b3bfc5650be6584c5c95fce447fa66fb918a83

Thanks,
Matthew Roy
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: IPv6 Status

[Sage Weil]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1022 bytes --]

Hi Matthew,

On Mon, 7 Jun 2010, Matthew Roy wrote:
> On 2009-10-02 there was a commit "use sockaddr_storage; and some ipv6
> support groundwork" but I can't find any references to IPv6 support
> being completed. Did that commit actually complete IPv6 support or are
> more changes still required?
> 
> Commit diff:
> http://ceph.newdream.net/git/p=ceph.git;a=commitdiff;h=dd732cbfc1c92f0d8dba2743a979baad6685a98c;hp=18b3bfc5650be6584c5c95fce447fa66fb918a83

I think all the basic groundwork is there.  The entity_addr_t type used 
throughout contains a sockaddr_storage, which can hold either ipv4 or ipv6 
addresses, and that commit updated the parsing function to handle v6 
address syntax.

The last step is just to update msg/SimpleMessenger.cc to actually bind or 
connect an ipv6 socket.  It should be pretty straightforward to fix the 
various places in the bind(), accept(), and connect() methods to do that, 
particularly if you already have v6 networking set up in your 
environment.

sage