Status Update
Comments
ma...@google.com <ma...@google.com>
ma...@google.com <ma...@google.com> #2
Hello,
Thank you for reaching out to us!
Could you please let us know if the issue is still persisting? If yes, please provide any additional information to understand the issue better and resolve the problem. Please fFile a ticket here](
In case you want to report a new issue, please do not hesitate to create a new
Thanks and Regards,
Mahaboob
ma...@google.com <ma...@google.com> #3
ma...@google.com <ma...@google.com>
ma...@google.com <ma...@google.com> #4
Hello,
Marking this case as Not Reproducible as we cannot proceed further without the requested information. In case you want to report a new issue, please feel free to create a new
Thanks & Regards,
Mahaboob Subhani
Google Cloud Support
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
I would like to request the internal IPv6 custom route that should be supported when configuring the next hop as a VM instance without the default internet gateway as it is supported in IPv4.
If we configure the custom route for IPv6 with the next hop as a VM instance without the default internet gateway(::/0), we will get an error as “Destination needs to have an internet gateway”. In the google documentation [1] states that it is currently not supported and the only supported IPv6 route is the default route (::/0), with the next-hop-gateway set to default-internet-gateway.
When we test the same environment with IPv4 as the next hop as a VM instance without the default internet gateway and it will work fine.
What you expected to happen:
As we need internal connectivity of the VMs, The custom route should support the routes without default internet gateway when we configure our next hop as a VM instance for IPv6.
Steps to reproduce:
Create the 3 VM instances with IPv6 and custom VPC.
Enable IP forwarding in one VM instance.(gateway instance)
Delete the default internet gateway (::/0)
Adding the custom route as a VM instance is the next hop which is IP forwarding enabled.
Other information (workarounds you have tried, documentation consulted, etc):
[1]