From e29537eaec541b1a898b4c6c59b970d665c23e91 Mon Sep 17 00:00:00 2001 From: Jeleel Muibi Date: Thu, 9 Jul 2026 20:27:52 +0100 Subject: docs: clarify Google Cloud peer gateway wording (cherry picked from commit 7662f4c3684fbc684228e0bda2ef4594f49a0e9a) --- docs/configexamples/gcp-ha-vpn-bgp.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/configexamples/gcp-ha-vpn-bgp.md b/docs/configexamples/gcp-ha-vpn-bgp.md index 53cad509..40b49ce3 100644 --- a/docs/configexamples/gcp-ha-vpn-bgp.md +++ b/docs/configexamples/gcp-ha-vpn-bgp.md @@ -14,8 +14,8 @@ interfaces and BGP over link-local `/30` address ranges for dynamic routing. - A Google Cloud HA VPN gateway with tunnels on both gateway interfaces. - A Cloud Router with BGP enabled. -- An external peer VPN gateway resource with two interfaces representing - the two VyOS edge peers. +- An external VPN gateway resource in Google Cloud with two interfaces, + where each interface represents one VyOS edge peer. - Manual BGP IPv4 next-hop addresses from unique `/30` ranges inside `169.254.0.0/16`. - Firewall policy that permits UDP 500, UDP 4500, and ESP from the two @@ -70,10 +70,13 @@ adjust the export policy for the other peer. ## Google Cloud configuration On the Google Cloud side, create an HA VPN gateway, a Cloud Router, an -external peer VPN gateway resource, and two VPN tunnels: +external VPN gateway resource that represents the two VyOS edge peers, and +two VPN tunnels: - This example follows the topology for two separate peer VPN gateways, each with one interface and one public IP address. +- In Google Cloud, model those two peer gateways as one external VPN gateway + resource with two interfaces. - Tunnel 0 connects HA VPN interface 0 to VyOS edge 1. - Tunnel 1 connects HA VPN interface 1 to VyOS edge 2. - The Cloud Router interface for tunnel 0 uses `169.254.10.2/30` and peers -- cgit v1.2.3