From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from duke.felloff.net ([216.126.196.34]) by ewsd; Mon Oct 14 12:42:20 EDT 2019
Message-ID: <0140C07E906BEF0CBCC4815EC4759F89@felloff.net>
Date: Mon, 14 Oct 2019 18:42:12 +0200
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] ipv6 setting
In-Reply-To: BC6C12E211F45C8DEADD1303C4690524@hera.eonet.ne.jp
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: hypervisor callback table 

ipv6 is a wide topic...

the nora6= environment variable just disables ipv6 autoconfiguration
on bootup. see /rc/bin/^(termrc cpurc) and /sys/src/9/boot/net.rc.

we handle ipv6 autoconfiguration like dhcp in ndb... that is, if
your machine has a ndb entry, but no ip addresses specified, we'll
try dhcp and slaac (unless disabled with nora6=) to get an address.

for static ipv6 address its the same as ipv4... you just specify
an ipv6 address using the ip= attribute.

for autoconfiguration to work, you need to have actual ipv6 router
on your network that sends router advertisements for the network
prefix. plan9 can do this with ip/ipconfig ra6 sendra 1 ...

note, that we do not have a dhcpv6 *CLIENT* in 9front yet. tho
we have a server (ip/dhcp6d) that can provide information like
dns and bootp server for foreign clients (uefi/windows).

i'm not quite convinced that the 12 second wait time is due to
ipv6 tho... it might be that we try to connect to the secstore
server and icmp being filtered in the network?

--
cinap