Op 13-05-2022 om 11:39 schreef Wei ZHOU:
Hi Wido,
We do not allocate an ipv6 subnet to a VPC. Instead, we allocate an ipv6
subnet for each vpc tier.
These subnets have the same gateway (ipv6 addr in VR).
for example
ipv6 route fd23:313a:2f53:3111::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4
ipv6 route fd23:313a:2f53:3112::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4
ipv6 route fd23:313a:2f53:3113::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4
Thanks Wei and Alex, that explains! So you can have multiple /64 subnets
being routed to the same VR.
It's up to the organization to only allocate /64s coming from a specific
/56 or /48 to make things logical, but underneath it's all /64s which we
need to route.
Wido
-Wei
On Fri, 13 May 2022 at 11:30, Wido den Hollander <w...@widodh.nl> wrote:
Op 12-05-2022 om 16:10 schreef Alex Mattioli:
ipv6 route fd23:313a:2f53:3cbf::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4
That's correct
Ok. So in that case the subnet would be very welcome to be present in
the message on the bus.
Or a larger subnet:
ipv6 route fd23:313a:2f53:3c00::/56 fd23:313a:2f53:3000:1c00:baff:fe00:4
Not really, the subnets for isolated/VPC networks are always /64. Which
means also no real need to include subnets as well.
But there can be multiple networks behind the VPC router or not? If
there are multiple networks you need >/64 as you can then allocate /64s
from that larger subnet.
Wido
Cheers
Alex
