How to use Windows Server 2019 DHCP for IPv6 with PfSense DHCPv6 RA?
-
I cannot quite figure out how to set this up correctly and I am hoping someone can help me get this working correctly.
In pfSense I have configured DHCPv6 RA As below:
Router Mode : Asssisted
Router Priority: Normal
Subnets: fd99:9971:: /64
DNS Config: Server 1: fd99:9971::10:100:1:1
Domain Search list : ghataura.netOn my Windows DHCP I have IPv6 Scope configured for subnet fd99:9971:: /64 and the Ipv6 address of the sever set to fd99:9971::10:100:1:1
What I am finding odd is that my Windows and Linux systsm are all getting 2 IPv6 addresses with the prefix fd99:9971::, of which 1 is from the
DHCP server, however some of my other devices (Andriod and IOS) are also getting 2 IPv6 addresses with the prefix fd99:9971:: but none of these seem
to be from the DHCP server.Asssisted mode seems to be only setting that I have found to work with the DHCP server and IPv6.
DHCPv6 on pfSense is disabled so I know that its not being generating there.
-
IPv6 address autoconfiguration is a world of fun all its own.
Assisted also sets up SLAAC, which is likely the source of the extra addresses, but maybe isn't what you want. In fact you probably don't want pfSense doing DHCPv6 at all, only RA. So you should set the Router mode to Router Only.
Though you may want SLAAC since Android (and maybe iOS?) do not support pulling IPv6 addresses via DHCPv6, only SLAAC.
Windows and Linux get two because they support both.
Much of this is left up to the client on IPv6, and there is only so much you can do from the server side, no matter which server it is.
-
@jimp Thanks for the information,. I'll give router only for a few days and see how that pans out, otherwise I guess I will stick with Asssisted.
