@mystic330
For answers, you have to ask them to show up.
Easy :
3bbf99cf-1805-4367-bd0c-efe70fdafa08-image.png
From this moment, the answers will be shown here : Status > System Logs > DHCP
When you see this part (can exists multiple times, as many as you have LAN interfaces with "IPv6 : Tracking" activated ) :
ac7043b6-2c35-4a38-b791-994446ba61e7-image.png
Here you can see I received one prefix.
As I have my LAN using IPv6 Tracking :
e263485d-1e5d-4e1e-bc26-cd933d135211-image.png
together with, on the same LAN Interface settings page :
efa378d5-8893-4bd1-8a60-0bc112e6dd07-image.png
Note the "from 0 to 0" which means that there is one (with index 0) available
Now, goto DHCPv6 Server page for my LAN interface :
8efe11b0-a10c-4f18-8b9f-bf5cafa618c3-image.png
You can see the prefix again, and the available network.
I've created a pool, from ::2 to ::86.
I've set the Router Advertisement to Managed (because : why not) :
b13cdfa3-21dd-4d23-8328-7cc3fdb1c3e8-image.png
and from now on my DHCP6 server starts to receive IPv6 lease requests.
Because I can see it happen in the ...... DHCP Logs :
67e2811a-5d6c-40ef-8eb2-d00822a64215-image.png
and the DHCP6 Leases pages starts to fill up :
df788617-8227-4c7d-a653-a965eac8351b-image.png
Note that most if not every DHCP6 lease are not taken from the pool.
I've set up Static DHCP6 Leases, like the IPv4 equivalent :
4704049d-5755-4087-b3bf-e945b70c9af1-image.png
Last, but not least : My DHCP6 WAN settings :
8bc89154-4ca0-4b02-94f8-061fbf48f9a1-image.png
and I'm not sure that the one and only option I've checked is even needed.
Note : all this is valid for my setup, using my ISP router (not modem), and it it my router that gives to pfSense an IPv6 on the WAN side, and a prefix (just one !! or the ISP router says it has /56 == 256 prefixes avaible). So, I have Ipv6 working on one pfSense LAN.
And things get even better : impossible to open ports to this prefix so i can access IPv6 to access a device (my NAS) using IPv6.
Very few ISPs are fully IPv6 compliant, many have implementation issues, they do thing 'their way'. And they are not documenting their miss-interpretation. There is still a "IPv4 works, and IPv6 maybe, if you can make it work" culture.
I've been using this IPv6 ISP for nearly a decade https://tunnelbroker.net/, it is free, you have your own /48, so your good for 65535 LANs, each with its own /64. They handled IPv6 as it is written in the book. They actually wrote that book (RFC).
There was one condition, though : you had to go through https://ipv6.he.net/certification/ : they ware actually asked that you learned how to use IPv6 before using it.