You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.
Description
We'd like to enable IPv6, and one of the steps is configuring our BGP sessions to exchange ipv6 prefixes.
This is related to #13752 - both are required to set up a VPN and use it for IPv6 traffic.
New or Affected Resource(s)
google_compute_router_peer
Potential Terraform Configuration
resource"google_compute_router_peer""peer" {
name="my-router-peer"router="my-router"region="us-central1"peer_ip_address="169.254.1.2"peer_asn=65513advertised_route_priority=100interface="interface-1"# New fields:enable_ipv6=trueipv6_nexthop_address="2600:2d00:0000:0002:0000:0000:0000:0001"peer_ipv6_nexthop_address="2600:2d00:0:3::1"# short notation
}
Restrictions:
The nexthop fields can only be set if ipv6 is enabled
Either both nexthop fields must be set, or neither (defaults to automatic config)
Both nexthop fields must be in 2600:2d00:0:2::/64 or 2600:2d00:0:3::/64 range (see second documentation link below, not listed as part of API).
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Description
We'd like to enable IPv6, and one of the steps is configuring our BGP sessions to exchange ipv6 prefixes.
This is related to #13752 - both are required to set up a VPN and use it for IPv6 traffic.
New or Affected Resource(s)
google_compute_router_peer
Potential Terraform Configuration
Restrictions:
2600:2d00:0:2::/64
or2600:2d00:0:3::/64
range (see second documentation link below, not listed as part of API).References
The text was updated successfully, but these errors were encountered: