Friday, April 16, 2021

DHCPv6 implementation

Hey!

So I'm trying to migrate some IPv6 and am stuck with a weird problem and am wondering how others have approached this. Open to any suggestions for redesigns etc.

For reasons, we would like to use DHCPv6 statefully - give DNS servers and IP addresses from the DHCP and use the routers RA to announce the gw address (and possibly DNS as well as a backup) to the clients.

Currently using M & O flag on the router.

The problem is that with this configuration a Windows 10 client will assign an IPv6 address to itself with SLAAC and will prefer using that IP address for connections, instead of the one assigned by the DHCPv6. This somewhat defeats the purpose of using the DHCP server in the first place.

We would like to have clients use only the IPv6 addresses we are assigning by the DHCP. Is that an unreasonable expectation? How have you guys solved this?

EDIT:

Due to the fact that when I started experimenting with this, I was not using M & O flags, Windows would have kept using the IPv6 address it got first with SLAAC, till it would have timed out: https://i.ibb.co/pxqmdSz/image.png

Had to run: "netsh int ipv6 reset" to remove that IP - re-enable the interface and now I'm left with the DHCP IP only, which is good enough. In this environment I am not worried about people/devices assigning IPs for themselves in general.



No comments:

Post a Comment