At least not for me, my Windows box didn't get an IP if I enabled the Prefix for the internal interface, I had to leave that at off and manually do a DHCPv6 server.
According to the howto #1 in this forum, creating a prefix for an interface with "other config" checked should also put a ipv6 dhcp server with that data on that same interface.
But it doesn't seem to do that, at least my windows 7 box didn't get an IP.
So I had to delete the prefix and setup a dhcp v6 server on that interface, which worked.
As long as the prefix is there, you can't create another dhcp server on that interface.
Just click the 'other config' checkbox, this enables DHCPv6 as well using the values configured at Prefix Advertisements. That will get your Windows Clients to retrieve the DNS Server settings as well.
maybe i missunderstand but for me Prefix Advertisement work fine without need of dhcpv6.
It's two different way of getting ip : - prefix advertisement use radvd, it give ip and dns server ip using an arp like style (sorry for the easyest way to explain it ) - Dhcpv6 give same things but allow to make dynamic update in dns server so you can use dns name of the computer instead of the ip, you need an dhcpv6 compilient client .
As now, i have prefix advertiement activate but no dhcpv6 and ipv6 works fine for me (but i'm not using any windows at all, will try with one this week end)
If you type this in a cmd console : netsh interface ipv6 show address
As explained in the IPv6 tutorial, it also depends on the Client OS if you additionally need DHCPv6 for Auto-Configuring DNS as well. For Windows, you need both Prefix Advertisements for IP-Assignment as well as DHCPv6 for DNS-Settings.
