Missing something with ipv6

[icsy7867]

My ISP gives me a single /64 block, and I was hoping to share this across multiple interfaces/VLAN (About 3 in total,  not very many.

While I can easily track the WAN interface using the /64 block, this isnt ideal.

What I was going to try, was to create a DHCPv6 server for each interface with a /72 block, and then use a router advertisment.  This seems to work, and the clients on the specific interfaces do get a valid IPV6 address, but I cannot ping/access anything externally.

I.E: ping6 google.com does not get replies.  I feel like there is fundamentally something I am missing here, and was curious if anyone had any ideas what I am doing wrong (If this is even possible!)

Thank you!

Few additional details while I am thinking about it.
Ipv6 is enabled in the firewall settings.
I also added incoming and outgoing allow all rules for ipv6 on the interface.

[Patrick M. Hausen]

You cannot have anything smaller than /64 on a broadcast interface. Period. Bad news, but that is how IPv6 works.

ULA is dysfunctional for most scnearios. I recommend getting/borrowing one or more GUA /64s, for example from your company that might have a real assignment or from a friend with a fixed /56 from their ISP.. Then use NPT6 to translate to your ISP's /64 ...

Register for a tunnel with Hurricane Electric and use that prefix ..

HTH,
Patrick

[icsy7867]

Thanks for the explanation.

After reading that I decided to backup. I deleted all my dhcpv6 servers and I set a single interface to "tracked" and pointed it to my WAN that pulled the prefix.

My LAN interface pulls an ipv6, but I cannot ping6 from the WAB or the LAN.  It either just gets 100% packet loss or a "no route to host"