They are related in that I had both v4 and v6 addresses on my WAN interface - just delegation wasn’t working - and I clicked “release” based on a suggestion here, and both v4 and v6 DHCP stopped working altogether.
I not worried about the v4 issue - just found it odd - this is a v6 troubleshooting thread and I’m specifically looking at/posting logs from the “dhcp6c” processes and help on how to troubleshoot v6 on pfsense. I’m way beyond the router vs end-node, ip addressing, etc stage (CCIE for 15 years)
I was previously getting a v6 address on my WAN interface, so I know Starlink is handing out/supports DHCPv6 and I was also getting a gateway so I know RA was working. (Now I need to troubleshoot why it suddenly stopped)
(I didn't realize the Only send prefix checkbox was checked - as I was trying different options it must've gotten checked - Thanks, I'll uncheck that).
What wasn’t working is delegation of a /56 from Starlink and the first /64 (with ID 0) to my LAN interface. My LAN interface never reported a routable v6 address (which I believe is keeping my dhcpv6 server on the LAN interface from working). For those of you that have v6 delegation working from your ISP, do you have a routable v6 address from the delegated block assigned to your LAN interface?? I know this is not required as a link-local address as the gateway on the LAN will allow routing to work, but I never see any dhcpv6 leases being handed out and I believe not having a v6 address on the LAN interface is the reason….