Problem with DHCPv6 Server after changing from GUA to ULA
-
Version 22.01-RELEASE (amd64)
Windows Host was getting an address from the DHCPv6 Server where the interface was a GUA via Track Interface from WAN. All working well.
I later changed my mind and used an ULA on that Interface. I deleted the static mapping and all other settings in the GUI, disabled the whole interface and rebooted pfSense, even waited for some days, the outcome was all the same, the Windows Host didn't got an address from the DHCPv6 Server. SLAAC was working fine though. Didn't find any problems in the DHCPv6 Server Log.
I gave up on it and switched back to GUA, everything is working again, could make a static mapping (via StatusDHCPv6 Leases) again.
Now I am back on it with the same Windows Host and the same pfSense and tried it again and it is again not working. This time after trying everything again, like release the IPv6 Lease on the Windows Host and so on I decided to reset the DUID on that Host and that was all it took to get DHCPv6 working again, this time with ULA.
I don't think that it is a Windows Bug, so it might be that pfSense had saved the Static Mapping somewhere else hidden from me and that was the reason, it wasn't working? (But probably not because I had to do the static mapping again anyways). Some many months ago I had no problem switching the interface form ULA to GUA and vice versa, I am pretty sure.
