Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Nesta página, descrevemos as especificações que uma sessão do Border Gateway Protocol (BGP) de VPN precisa seguir e como criar uma sessão do BGP de VPN.
A VPN isolada do Google Distributed Cloud (GDC) oferece suporte ao roteamento dinâmico usando uma sessão BGP IPv4 para cada túnel de VPN. A sessão do BGP permite que os peers do BGP na rede remota e na organização do GDC anunciem rotas entre si.
Antes de começar
Para criar uma sessão do BGP de VPN, você precisa ter os papéis de identidade e acesso necessários:
Administrador da VPN: tem permissões de leitura e gravação em todos os recursos relacionados à VPN. Peça ao administrador do IAM da organização para conceder a você o papel de administrador de VPN (vpn-admin).
Leitor de VPN: tem permissões de leitura em todos os recursos relacionados à VPN. Peça ao administrador do IAM da organização para conceder a você o papel de leitor de VPN (vpn-viewer).
O peering do BGP na organização aceita um intervalo de keepalive do BGP de 30 segundos, com um timer de espera de 90 segundos.Para cada sessão do BGP, os endereços IPv4 precisam atender aos seguintes requisitos:
Cada endereço IPv4 do BGP precisa pertencer à mesma sub-rede /30 que se encaixa
no intervalo 169.254.0.0/16.
Cada endereço IPv4 do BGP é o primeiro ou o segundo host da sub-rede /30. O primeiro e o último endereços IP da sub-rede são reservados para endereços de rede e de transmissão.
Cada intervalo de endereços do BGP para cada sessão do BGP precisa ser exclusivo entre todas as sessões do BGP da VPN da organização.
A autenticação MD5 não é compatível. É um método de verificação da integridade e autenticidade dos dados usando o algoritmo de hash MD5.
Criar uma sessão do BGP de VPN
Para criar uma sessão do BGP para o túnel de VPN, siga estas etapas:
Crie um objeto VPNBGPPeer no cluster de administrador da organização no namespace da plataforma:
MANAGEMENT_API_SERVER: o caminho do kubeconfig do servidor de API zonal. Se você ainda não gerou um arquivo kubeconfig
para o servidor da API na zona de destino, consulte
Fazer login para mais detalhes.
VPN_BGP_PEER_NAME: o nome do peering do BGP da VPN.
REMOTE_PEER_NAME: o nome do peer do BGP na rede
remota.
REMOTE_PEER_IP: o endereço IPv4 do BGP da sub-rede /30
do peering do BGP na rede remota.
REMOTE_PEER_ASN: o número do sistema autônomo (ASN, na sigla em inglês)
configurado para a rede remota.
LOCAL_PEER_NAME: um nome para o peer do BGP na organização do GDC.
LOCAL_PEER_IP: o endereço IPv4 do BGP da sub-rede /30
do par BGP na organização do GDC.
LOCAL_PEER_ASN: o ASN configurado para a organização do GDC.
Verifique se o objeto VPN_BGP_PEER_NAME foi reconciliado corretamente examinando o campo Status. Confira os detalhes do objeto VPNBGPPeer:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-04 UTC."],[[["\u003cp\u003eThis document outlines the requirements and procedures for establishing a VPN Border Gateway Protocol (BGP) session within Google Distributed Cloud (GDC) air-gapped environments.\u003c/p\u003e\n"],["\u003cp\u003eCreating a VPN BGP session requires either the VPN Admin or VPN Viewer role, which can be granted by the Organization IAM Admin.\u003c/p\u003e\n"],["\u003cp\u003eEach VPN BGP session must use unique IPv4 addresses from a \u003ccode\u003e/30\u003c/code\u003e subnet within the \u003ccode\u003e169.254.0.0/16\u003c/code\u003e range, and addresses must be the first or second host in the subnet, with a keepalive interval of 30 seconds and a hold timer of 90 seconds.\u003c/p\u003e\n"],["\u003cp\u003eThe process of creating a BGP session for a VPN tunnel involves creating a \u003ccode\u003eVPNBGPPeer\u003c/code\u003e object with specific remote and local parameters, then verifying its status.\u003c/p\u003e\n"],["\u003cp\u003eMD5 authentication is not supported.\u003c/p\u003e\n"]]],[],null,["# Create a VPN BGP session\n\nThis page describes the specifications a VPN Border Gateway\nProtocol (BGP) session must adhere to and how to create a VPN BGP session.\n\nGoogle Distributed Cloud (GDC) air-gapped VPN supports dynamic routing using an IPv4 BGP session for each VPN tunnel. The BGP session lets the BGP peers\nin the remote network and in the GDC organization advertise routes to each\nother.\n\nBefore you begin\n----------------\n\nTo create a VPN BGP session, you must have the necessary identity and access roles:\n\n- VPN Admin: has read and write permissions on all VPN-related resources. Ask your Organization IAM Admin to grant you the VPN Admin (`vpn-admin`) role.\n- VPN Viewer: has read permissions on all VPN-related resources. Ask your Organization IAM Admin to grant you the VPN Viewer (`vpn-viewer`) role.\n- For more information, see [Role definitions](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/iam/role-definitions).\n\nVPN BGP session specifications\n------------------------------\n\nThe BGP peer in the organization supports a BGP keepalive interval of 30 seconds, with a hold timer of 90 seconds.For each BGP session, the IPv4 addresses must meet the following requirements:\n\n- Each BGP IPv4 address must belong to the same `/30` subnet that fits within the `169.254.0.0/16` range.\n- Each BGP IPv4 address is the first or second host of the `/30` subnet. The first and the last IP addresses of the subnet are reserved for network and broadcast addresses.\n- Each BGP address range for each BGP session must be unique among all VPN BGP sessions for the organization.\n\nMD5 authentication is not supported. This is a method of verifying the integrity and authenticity of data using the MD5 hashing algorithm.\n\nCreate a VPN BGP session\n------------------------\n\nTo create a BGP session for the VPN tunnel, follow these steps:\n\n1. Create a `VPNBGPPeer` object in the\n org admin cluster in the platform namespace:\n\n kubectl --kubeconfig \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e create -n platform -f - \u003c\u003cEOF\n apiVersion: networking.gdc.goog/v1\n kind: VPNBGPPeer\n metadata:\n name: \u003cvar translate=\"no\"\u003eVPN_BGP_PEER_NAME\u003c/var\u003e\n spec:\n remote:\n name: \u003cvar translate=\"no\"\u003eREMOTE_PEER_NAME\u003c/var\u003e\n ip: \u003cvar translate=\"no\"\u003eREMOTE_PEER_IP\u003c/var\u003e\n asn: \u003cvar translate=\"no\"\u003eREMOTE_PEER_ASN\u003c/var\u003e\n local:\n name: \u003cvar translate=\"no\"\u003eLOCAL_PEER_NAME\u003c/var\u003e\n ip: \u003cvar translate=\"no\"\u003eLOCAL_PEER_IP\u003c/var\u003e\n asn: \u003cvar translate=\"no\"\u003eLOCAL_PEER_ASN\u003c/var\u003e\n EOF\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e: the zonal API server's kubeconfig path. If you have not yet generated a kubeconfig file for the API server in your targeted zone, see [Sign in](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/iam/sign-in#cli) for details.\n - \u003cvar translate=\"no\"\u003eVPN_BGP_PEER_NAME\u003c/var\u003e: the name of the VPN BGP peer.\n - \u003cvar translate=\"no\"\u003eREMOTE_PEER_NAME\u003c/var\u003e: the name for the BGP peer in the remote network.\n - \u003cvar translate=\"no\"\u003eREMOTE_PEER_IP\u003c/var\u003e: the BGP IPv4 address from the `/30` subnet of the BGP peer in the remote network.\n - \u003cvar translate=\"no\"\u003eREMOTE_PEER_ASN\u003c/var\u003e: the Autonomous System Number (ASN) configured for the remote network.\n - \u003cvar translate=\"no\"\u003eLOCAL_PEER_NAME\u003c/var\u003e: a name for the BGP peer in the GDC organization.\n - \u003cvar translate=\"no\"\u003eLOCAL_PEER_IP\u003c/var\u003e: the BGP IPv4 address from the `/30` subnet of the BGP peer in the GDC organization.\n - \u003cvar translate=\"no\"\u003eLOCAL_PEER_ASN\u003c/var\u003e: the ASN configured for the GDC organization.\n2. Verify that the \u003cvar translate=\"no\"\u003eVPN_BGP_PEER_NAME\u003c/var\u003e object was correctly reconciled by examining the `Status` field. Get the details of the `VPNBGPPeer` object:\n\n kubectl --kubeconfig \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e describe -n platform vpnbgppeer \u003cvar translate=\"no\"\u003eVPN_BGP_PEER_NAME\u003c/var\u003e\n\n Examine the output, it must look similar to the following example: \n\n Status:\n Conditions:\n Last Transition Time: 2024-05-10T00:26:13Z\n Message: Ready\n Observed Generation: 1\n Reason: Ready\n Status: True\n Type: ValidIPs\n Last Transition Time: 2024-05-10T00:26:00Z\n Message: Used by 0 VPNTunnels, must be used by a single VPNTunnel\n Observed Generation: 1\n Reason: GetResourceFailed\n Status: False\n Type: TunnelsAttached\n Last Transition Time: 2024-05-10T00:26:00Z\n Message: TunnelsAttached or ValidIPs Condition not Ready.\n Observed Generation: 1\n Reason: Unknown\n Status: False\n Type: Reconciled\n Last Transition Time: 2024-05-10T00:26:01Z\n Message: ValidIPs or Reconciled Condition not Ready.\n Observed Generation: 1\n Reason: Unknown\n Status: False\n Type: AdvertisedRoutesReady\n Last Transition Time: 2024-05-10T00:26:13Z\n Message: Ready\n Observed Generation: 1\n Reason: Ready\n Status: True\n Type: ReceivedRoutesValid\n Last Transition Time: 2024-05-10T00:26:01Z\n Message: TunnelsAttached Condition not Ready.\n Observed Generation: 1\n Reason: Unknown\n Status: False\n Type: ReceivedRoutesReady\n Last Transition Time: 2024-05-10T00:26:01Z\n Message: Condition \"TunnelsAttached\" is not ready.\n Observed Generation: 1\n Reason: NotReady\n Status: False\n Type: Ready\n ```\n\nThe `VPNBGPPeer` must be attached to a `VPNTunnel`. We handle this step in [Create a VPN Tunnel](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/vpn/configure-the-tunnel#create-a-vpn-tunnel).\n\nWhat's next\n-----------\n\n- [Create the secret with a PSK](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/vpn/create-secret)"]]
