Hmm, I thought these prefixes a subset of the CIDR provided through RA on WAN?
I am kind of in similar situation as parent poster. My ISP supposedly provides IPv6, but from the RA announcements it looks like it is /64. My assuption was that I supposed to split it myself into smaller pieces. It's also sucks since they are providing /64 which is the smallest CIDR that SLAAC requires.
When I called my ISP they said that I only have IPv4, so it's not like I can get much help with IPv6.
Although I know IPv6 works, because when I connected a box and told it to configure itself through RA it did and I was able to ping ipv6 hosts.
Nope, the WAN and LAN networks need to use different, non-overlapping network ranges. The only automated way to get the LAN prefix is to ask the ISP via DHCPv6-PD.
Routing in v6 is exactly the same as in v4. If your ISP gives you 203.0.113.42/24 on the WAN, you can't turn around and use other parts of 203.0.113.x on the LAN. The only difference is that in v6 you actually get a routed prefix, and that DHCPv6-PD exists to automate it.
I am kind of in similar situation as parent poster. My ISP supposedly provides IPv6, but from the RA announcements it looks like it is /64. My assuption was that I supposed to split it myself into smaller pieces. It's also sucks since they are providing /64 which is the smallest CIDR that SLAAC requires.
When I called my ISP they said that I only have IPv4, so it's not like I can get much help with IPv6.
Although I know IPv6 works, because when I connected a box and told it to configure itself through RA it did and I was able to ping ipv6 hosts.