From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4e6ad3e53d1ab78e243c7f847040a2d6@fritz.wgti.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ipv6
Date: Fri, 20 Apr 2007 16:46:08 -0700
From: Tim Wiess <tim@nop.cx>
In-Reply-To: <81b82789a72972f04fd6ad1f7b554177@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 4d82891c-ead2-11e9-9d60-3106f5b1d025

    Geoff,
    Thanks! I'm using v6 quite a bit on my network, so I'll
    cetainly be testing these changes.

    Tim


> Over the last two days I've pushed out a new ipconfig, some small
> utilities, and changes to the kernel and manual pages.  ipconfig(8) is
> a good place to start.  ipconfig is now able to configure more of the
> ipv6 stack, in particular automatically configuring the link-local
> address and enabling sending or receiving of router advertisements.
> 
> I haven't been able to test the IPv6 functionality very thoroughly
> here, though it does seem to work at least minimally.  Feedback on the
> new ipconfig from people who are using IPv6 is welcomed.
> 
> The ipv6 attribute is now documented in ndb(6), but the trade-off
> between just using an ip attribute with an IPv6 address and using the
> ipv6 attribute is not yet obvious to me.
> 
> One thing we don't have yet is DHCPv6.  The sheer size of the stack of
> paper that is the DHCPv6 RFCs is daunting.