- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Just to be sure, let me just repeat it differently?
You're using this 100.64.0.0/10 network in your on premises environment and plan to reach it from your VMs located in VMware Cloud on AWS, right?
If so, you need to read this KB explaining it in details: https://kb.vmware.com/s/article/76022
You will see at the end that resolutions are:
- Do not use the IP range - (100.64.0.0–100.127.255.255) addresses. They are always meant to be intermediary relay hops that are internal to the carrier networks.
- VMC uses the same network and specification to implement CGN style networking between the VMC Edge routers in internal routing components which can create a conflict.
- SDDCs that were created using version 1.10 or later have a smaller allocation of 100.64.0.0/16 instead of the entire 100.64.0.0/10 block. Address space other than the 100.64.0.0/16 block can be used for endpoints.
- SDDCs that were upgraded from releases prior to 1.10 do not reflect this change and will continue to have the 100.64.0.0/10 allocation present.
- VMC also uses this IP range between internal routing components it will create a conflict.
- If a packet with either a source or a destination address in the 100.64 address space that conflicts with overlapping address space internal to the SDDC, it will be delivered inside the edge and will never egress.
Hope that helps and looking forward to read your comments
Cheers
Emmanuel BERNARD
Lead Solution Engineer | VMware Cloud | EMEA
Please mark "Helpful" or "Correct Answer" if applies. Appreciate it.
Lead Solution Engineer | VMware Cloud | EMEA
Please mark "Helpful" or "Correct Answer" if applies. Appreciate it.