Configurar endereços IPv6 para instâncias e modelos de instância
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
É possível configurar endereços IPv6 em uma instância do Compute Engine se a
sub-rede à qual a instância está conectada tiver um intervalo IPv6 configurado.
As instâncias de computação que têm configurações IPv4 e IPv6 são de pilha dupla.
O endereço IPv6 é adicionado a todos os endereços IPv4 configurados na
interface de rede.
As interfaces em instâncias de pilha dupla ou somente IPv6 são alocadas para um único intervalo /96
de endereços IPv6. O primeiro endereço IPv6 no intervalo (/128) é
configurado na interface.
Qualquer interface na instância pode ter endereços IPv6 configurados. Para mais
informações sobre como configurar várias interfaces de rede, consulte
Várias interfaces de rede.
O tipo de pilha da interface de rede de uma VM determina o tipo de sub-redes
a que ela pode se conectar:
As interfaces somente IPv4 podem se conectar a sub-redes de pilha dupla e somente IPv4.
As interfaces de pilha dupla podem se conectar a sub-redes de pilha dupla.
As interfaces somente IPv6 podem se conectar a sub-redes de pilha dupla e somente IPv6
(Pré-lançamento).
Para configurar endereços IPv6 em uma interface de rede, ela precisa estar
conectada a uma sub-rede
de pilha dupla ou somente IPv6
(Pré-lançamento).
A configuração do tipo de acesso IPv6 de uma sub-rede determina se a sub-rede tem um
intervalo IPv6 interno ou externo. As instâncias conectadas herdam o tipo de acesso
IPv6 da sub-rede.
As instâncias somente IPv6 (Pré-lançamento) são aceitas
apenas com o Ubuntu e o Debian OS.
Como acessar instâncias usando endereços IPv6
A regra de firewall de entrada de negação IPv6 implícita protege as instâncias bloqueando as conexões recebidas para os endereços IPv6 delas.
Para acessar instâncias usando os endereços IPv6, você precisa ter uma regra de prioridade
mais alta que permita o acesso de entrada.
A lista a seguir descreve como os endereços IPv6 são atribuídos a instâncias de computação.
As instâncias de computação recebem um endereço IPv6 usando o DHCPv6. O servidor de
metadados responde às solicitações DHCPv6 da instância e envia o primeiro
endereço IPv6 (/128) do intervalo /96 alocado em resposta.
O servidor de metadados usa a divulgação de rota para publicar a rota padrão na
instância. A instância pode usar essa rota padrão para todo o tráfego IPv6.
Para encontrar a rota padrão da interface de rede de uma instância,
conecte-se a ela e consulte a entrada
gateway-ipv6 no servidor de metadados.
As instâncias de computação são configuradas com endereços IP locais de link, que são
atribuídos do intervalo fe80::/10, mas são usados apenas para
descoberta de vizinhos.
A configuração da MTU na interface de rede da instância se aplica aos
pacotes IPv4 e IPv6, mas nem todos os valores de MTU são compatíveis em todas as
circunstâncias. Saiba mais em
Unidade de transmissão máxima.
Criar uma instância que usa endereços IPv6
É possível criar uma instância que use uma combinação de endereços IPv4 e IPv6 (pilha dupla) ou que use apenas endereços
IPv6.
Para saber como criar uma instância do Compute Engine que usa
endereços IPv6, consulte as seguintes tarefas:
É possível mudar o tipo de pilha de uma instância do Compute Engine.
O tipo de pilha pode ser definido como:
Somente IPv4 (pilha única)
IPv4 e IPv6 (pilha dupla)
Se você estiver mudando o tipo de pilha para pilha dupla, a instância precisará estar conectada
a uma sub-rede de pilha dupla. Se você precisar mudar a sub-rede a que a instância está
conectada, interrompa a instância e mude a sub-rede. Depois que a sub-rede for
atualizada, será possível mudar o tipo de pilha de IP da instância.
Não é possível mudar o tipo de pilha de uma instância somente IPv6
(pré-lançamento).
PROJECT_ID: o ID do projeto que contém a instância.
ZONE: a zona em que a instância está implantada.
INSTANCE_NAME: o nome da instância.
Exemplo de corpo da solicitação:
{
"stackType": "STACK_TYPE",
}
Substitua STACK_TYPE pelo tipo de pilha da instância:
IPV4_ONLY ou IPV4_IPV6.
Criar um modelo de instância com endereços IPv6
É possível criar um modelo de instância regional ou global que pode ser usado para criar
instâncias de pilha dupla ou apenas IPv6 (pré-lançamento).
Para mais informações, consulte
Criar modelos de instâncias.
Use a CLI do Google Cloud ou o REST para criar um modelo de instância
que crie instâncias que usam endereços IPv6.
gcloud
Para criar um modelo de instância regional ou global, use o
comando gcloud compute instance-templates create.
Se você quiser criar um modelo de instância regional, use a sinalização --instance-template-region para especificar a região do modelo de instância.
O exemplo a seguir cria um modelo de instância global:
Por exemplo, se você especificar
"sourceImage": "projects/debian-cloud/global/images/family/debian-12",
o Compute Engine vai criar uma instância a partir da versão mais recente da
imagem do sistema operacional na família de imagens Debian 12.
[[["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-08-18 UTC."],[[["\u003cp\u003eCompute Engine instances can be configured with IPv6 addresses if the connected subnet has an IPv6 range, enabling dual-stack (IPv4 and IPv6) or IPv6-only configurations.\u003c/p\u003e\n"],["\u003cp\u003eInstances with dual-stack or IPv6-only configurations are allocated a single /96 range of IPv6 addresses, with the first /128 address configured on the interface, and can only be connected to dual-stack or IPv6-only subnets.\u003c/p\u003e\n"],["\u003cp\u003eIPv6-only instances, currently in preview, are only supported with Ubuntu and Debian operating systems, and their stack type cannot be changed after creation.\u003c/p\u003e\n"],["\u003cp\u003eAccessing instances via IPv6 addresses requires a firewall rule that allows incoming connections, overriding the default implied deny rule for IPv6 ingress traffic.\u003c/p\u003e\n"],["\u003cp\u003eYou can create dual-stack or IPv6-only instances using instance templates that are defined via Google Cloud CLI or REST, enabling you to define which OS, subnet, and stack type they will have.\u003c/p\u003e\n"]]],[],null,["# Configure IPv6 addresses for instances and instance templates\n\n*** ** * ** ***\n\nYou can configure IPv6 addresses on a Compute Engine instance if the\nsubnet that the instance is connected to has an IPv6 range configured.\n\nFor more information about IPv6, see\n[IPv6 subnet ranges](/vpc/docs/subnets#ipv6-ranges).\n\nSpecifications\n--------------\n\n- Compute instances that have both IPv4 and IPv6 configurations are *dual-stack*.\n The IPv6 address is in addition to any IPv4 addresses that are configured on\n the network interface.\n\n- Interfaces on dual-stack or IPv6-only instances are allocated a single `/96`\n range of IPv6 addresses; the first IPv6 address in the range (`/128`) is\n configured on the interface.\n\n- Any interface on the instance can have IPv6 addresses configured. For more\n information about configuring multiple network interfaces, see\n [Multiple network interfaces](/vpc/docs/multiple-interfaces-concepts).\n\n- The stack type of an VM's network interface determines the type of subnets\n to which it can connect:\n\n - IPv4-only interfaces can connect to dual-stack and IPv4-only subnets.\n - Dual-stack interfaces can connect to dual-stack subnets.\n - IPv6-only interfaces can connect to dual-stack and IPv6-only subnets.\n- To configure IPv6 addresses on a network interface, the interface must be\n connected to a dual stack or IPv6-only\n [subnet](/vpc/docs/subnets#subnet-types).\n\n- A subnet's IPv6 access type configuration determines whether the subnet has an\n internal or external IPv6 range. Connected instances inherit the IPv6 access\n type from the subnet.\n\n- IPv6-only instances are supported with only Ubuntu and Debian OS images.\n\nAccessing instances using IPv6 addresses\n----------------------------------------\n\nThe [implied IPv6 deny ingress firewall rule](/vpc/docs/firewalls#default_firewall_rules)\nprotects instances by blocking incoming connections to their IPv6 addresses.\nTo access instances using their IPv6 addresses, you must have a higher priority\nrule that allows incoming access.\n\nFor more information about firewall rules, see\n[VPC firewall rules](/firewall/docs/firewalls) and\n[Hierarchical firewall policies](/firewall/docs/firewall-policies).\n\nFor examples of VPC firewall rules, see\n[Configure firewall rules for common use cases](/vpc/docs/using-firewalls#rules-for-common-use-cases).\n\nIPv6 address assignment\n-----------------------\n\nThe following list describes how IPv6 addresses are assigned to compute\ninstances.\n\n- Compute instances are assigned an IPv6 address using DHCPv6. The metadata\n server responds to the instance's DHCPv6 requests and sends the first\n IPv6 address (`/128`) from the allocated `/96` range in response.\n\n- The metadata server uses route advertisement to publish the default route to\n the instance. The instance can then use this default route for all IPv6\n traffic.\n\n You can find the default route for an instance's network interface by\n connecting to the instance and querying the metadata server for the\n `gateway-ipv6` entry. \n\n ```\n curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/gateway-ipv6 -H \"Metadata-Flavor: Google\"\n ```\n\n For more information about the metadata server, see\n [View and query instance metadata](/compute/docs/metadata/querying-metadata).\n- Compute instances are configured with link local IP addresses, which are\n assigned from the `fe80::/10` range, but they are used only for\n [neighbor discovery](https://en.wikipedia.org/wiki/Neighbor_Discovery_Protocol).\n\n- The MTU configuration on the instance's network interface applies to both\n IPv4 and IPv6 packets, but not all MTU values are supported in all\n circumstances. For more information, see\n [Maximum transmission unit](/vpc/docs/mtu).\n\nCreate an instance that uses IPv6 addresses\n-------------------------------------------\n\nYou can create an instance that uses either a combination of IPv4 and IPv6\naddresses (*dual-stack*), or you can create an instance that uses only IPv6\naddresses.\n\nFor information about how to create a Compute Engine instance that uses\nIPv6 addresses, see the following tasks:\n\n- [Create a dual-stack instance](/compute/docs/instances/create-ipv6-instance#create-vm-ipv6-dual)\n- [Create an IPv6-only instance](/compute/docs/instances/create-ipv6-instance#create-vm-ipv6-only)\n\nChange the stack type of an instance\n------------------------------------\n\nYou can change the stack type of an existing Compute Engine instance.\nThe stack type can be set to either of the following:\n\n- IPv4 only (single stack)\n- IPv4 and IPv6 (dual-stack)\n\nIf you are changing the stack type to dual-stack, the instance must be connected\nto a dual-stack subnet. If you need to change which subnet the instance is\nconnected to, stop the instance and change the subnet. After the subnet is\nupdated, you can change the instance's IP stack type.\n\nYou can't change the stack type of an IPv6-only instance. \n\n### Console\n\n1. Go to the **VM instances** page.\n\n\n [Go to VM instances](https://console.cloud.google.com/compute/instances)\n2. Click the name of the instance that you want to assign an IPv6 address to.\n\n3. From the instance details page, complete the following steps:\n\n 1. Click **Edit**.\n 2. In **Network interfaces**, expand the interface that you want to edit.\n 3. Select the **IP stack type** : **IPv4 only (single-stack)** or **IPv4 and IPv6 (dual-stack)**.\n 4. Click **Done**.\n4. Click **Save**.\n\n### gcloud\n\nUpdate the stack type of an instance by using the\n[`gcloud compute instances network-interfaces update`\ncommand](/sdk/gcloud/reference/compute/instances/network-interfaces/update) \n\n```\ngcloud compute instances network-interfaces update INSTANCE_NAME \\\n --stack-type=STACK_TYPE \\\n --zone=ZONE\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eINSTANCE_NAME\u003c/var\u003e: the name of the instance.\n- \u003cvar translate=\"no\"\u003eSTACK_TYPE\u003c/var\u003e: the stack type for the instance: `IPV4_ONLY` or `IPV4_IPV6`.\n- \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: the zone that the instance is deployed in.\n\n### REST\n\nUpdate the stack type of an instance by making a `PATCH` request to the\n[`instances.updateNetworkInterface`\nmethod](/compute/docs/reference/rest/v1/instances/updateNetworkInterface). \n\n```\nPATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances/INSTANCE_NAME/updateNetworkInterface\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the project that contains the instance.\n- \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: the zone that the instance is deployed in.\n- \u003cvar translate=\"no\"\u003eINSTANCE_NAME\u003c/var\u003e: the name of the instance.\n\nExample request body: \n\n```\n{\n \"stackType\": \"STACK_TYPE\",\n}\n```\n\nReplace \u003cvar translate=\"no\"\u003eSTACK_TYPE\u003c/var\u003e with the stack type for the instance:\n`IPV4_ONLY` or `IPV4_IPV6`.\n\nCreate an instance template with IPv6 addresses\n-----------------------------------------------\n\nYou can create a regional or global instance template that can be used to create\ndual-stack or IPv6-only instances. For more information, see\n[Create instance templates](/compute/docs/instance-templates/create-instance-templates).\n\nYou must use the Google Cloud CLI or REST to create an instance\ntemplate that creates instances that use IPv6 addresses. \n\n### gcloud\n\nTo create a regional or global instance template, use the\n[`gcloud compute instance-templates create` command](/sdk/gcloud/reference/compute/instance-templates/create).\nIf you want to create a regional instance template, you must use the\n`--instance-template-region` flag to specify the region for the instance\ntemplate.\n\nThe following example creates a global instance template: \n\n```\ngcloud compute instance-templates create TEMPLATE_NAME \\\n --subnet=SUBNET \\\n --stack-type=STACK_TYPE\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eTEMPLATE_NAME\u003c/var\u003e: the name for the template.\n- \u003cvar translate=\"no\"\u003eSUBNET\u003c/var\u003e: a subnet that has an IPv6 subnet range.\n- \u003cvar translate=\"no\"\u003eSTACK_TYPE\u003c/var\u003e: the stack type, either IPV4_IPV6 for a dual-stack instance, or IPV6_ONLY for an instance with external IPv6 address.\n\n### REST\n\nTo create a regional instance template, use the\n[`regionInstanceTemplates.insert` method](/compute/docs/reference/rest/v1/regionInstanceTemplates/insert),\nor, to create a global instance template, use the\n[`instanceTemplates.insert` method](/compute/docs/reference/rest/v1/instanceTemplates/insert).\n\nThe following example creates a global instance template: \n\n```\nPOST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/global/instanceTemplates\n```\n\nReplace \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with the project ID.\n\nExample request body: \n\n```\n{\n \"name\": \"INSTANCE_TEMPLATE_NAME\"\n \"properties\": {\n \"machineType\": \"MACHINE_TYPE\",\n \"networkInterfaces\": [\n {\n \"subnetwork\": \"regions/REGION/subnetworks/SUBNET\",\n \"stackType\": \"STACK_TYPE\",\n },\n ],\n \"disks\":\n [\n {\n \"type\": \"PERSISTENT\",\n \"boot\": true,\n \"mode\": \"READ_WRITE\",\n \"initializeParams\":\n {\n \"sourceImage\": \"IMAGE_URI\"\n }\n }\n ]\n }\n}\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eINSTANCE_TEMPLATE_NAME\u003c/var\u003e: the name of the instance template.\n- \u003cvar translate=\"no\"\u003eMACHINE_TYPE\u003c/var\u003e: the machine type of the instances. For example, `c3-standard-4`.\n- \u003cvar translate=\"no\"\u003eSUBNET\u003c/var\u003e: a subnet that has an IPv6 subnet range.\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the region of the subnet.\n- \u003cvar translate=\"no\"\u003eIMAGE_URI\u003c/var\u003e: the URI to the\n [image](/compute/docs/images) that you want to use.\n\n For example, if you specify\n `\"sourceImage\": \"projects/debian-cloud/global/images/family/debian-12\"`,\n Compute Engine creates an instance from the latest version of the\n operating system image in the Debian 12 image family.\n\nTo learn more about request parameters, see the\n[`instanceTemplates.insert` method](/compute/docs/reference/rest/v1/instanceTemplates/insert)."]]