Yes, SLAAC by default provides the address and default gateway (RA) If SLAAC managed flag is set, then DHCPv6 is used get the address and other configs (DNS, etc..) If SLAAC other flag is set, then SLAAC provides the address, and uses DHCPv6 to get the other configs (DNS, etc..) With SLAAC and without DHCPv6 the device has no way of knowing the DNS server and other configs such as search domain, etc... RFC 6106 provides a new feature that allows devices to obtain DNS from RA, but not all devices and network equipment support it yet. For devices that don't support RFC 6106 or DHCPv6, then it has to use IPv4 (DHCPv4) to get the IPv4 DNS address. -----Original Message----- From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Nicholas Warren Sent: Thursday, October 15, 2015 11:21 AM To: Dave Bell <me@geordish.org> Cc: nanog@nanog.org Subject: RE: Android and DHCPv6 again Excuse my ignorance, but can DHCPv6 and SLAAC be run in parallel? Thank you, - Nich
-----Original Message----- From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Dave Bell Sent: Thursday, October 15, 2015 9:52 AM To: Ray Soucy Cc: nanog@nanog.org Subject: Re: Android and DHCPv6 again
On 15 October 2015 at 13:22, Ray Soucy <rps@maine.edu> wrote:
Android does not have a complete IPv6 implementation and should not be IPv6 enabled. Please do your part and complain to Google that Android does not support DHCPv6 for address assignment. I use android devices on my network with IPv6 connectivity, and no issues at all. It gets an address. Does DNS via IPv6, and can send packets over IPv6. I don't use or need DHCPv6.
You may not be able to roll out IPv6 to them because you need DHCPv6. In this case I suggest you complain to Google. Other people may not be able to roll out IPv6 to them because they need DHCPv6. They should also complain to Google. Suggesting that nobody rolls out IPv6 on them because they don't support one feature they may not even need is absurd. DHCPv6 is not a prerequisite for IPv6.
Regards, Dave