Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/vpc/docs/subnets below:

Subnets | VPC | Google Cloud

Stay organized with collections Save and categorize content based on your preferences.

Virtual Private Cloud (VPC) networks are global resources. Each VPC network consists of one or more IP address ranges called subnets. Subnets are regional resources, and have IP address ranges associated with them.

In Google Cloud, the terms subnet and subnetwork are synonymous. They are used interchangeably in the Google Cloud console, Google Cloud CLI commands, and API documentation.

A network must have at least one subnet before you can use it. Auto mode VPC networks create subnets in each region automatically. Custom mode VPC networks start with no subnets, giving you full control over subnet creation. You can create more than one subnet per region. For information about the differences between auto mode and custom mode VPC networks, see types of VPC networks.

When you create a resource in Google Cloud, you choose a network and subnet. For resources other than instance templates, you also select a zone or a region. Selecting a zone implicitly selects its parent region. Because subnets are regional objects, the region that you select for a resource determines the subnets that it can use:

• When you create a virtual machine (VM) instance, you select a zone for the instance. If you don't select a network for the VM, the default VPC network is used, which has a subnet in every region. If you do select a network for the VM, you must select a network that contains a subnet in the selected zone's parent region.

• When you create a managed instance group, you select a zone or region, depending on the group type, and an instance template. The instance template defines which VPC network to use. Therefore, when you create a managed instance group, you must select an instance template with an appropriate configuration; the template must specify a VPC network that has subnets in the selected zone or region. Auto mode VPC networks always have a subnet in every region.

• The process of creating a Kubernetes container cluster involves selecting a zone or region (depending on the cluster type), a network, and a subnet. You must select a subnet that is available in the selected zone or region.

VPC networks support subnets with the following stack types. A single VPC network can contain any combination of these subnets.

When you create a subnet, you specify which stack type to use. You can also change the stack type of a subnet in the following scenarios:

• If the subnet is IPv4-only, you can change it to dual-stack.
• If the subnet is dual-stack and has an external IPv6 address range, you can change it to IPv4-only.

Subnets with IPv6 address ranges are supported on custom mode VPC networks only. Subnets with IPv6 address ranges aren't supported on auto mode VPC networks or legacy networks.

When you create an IPv4 subnet range, you provide the following information:

When you create an IPv6 subnet range, you provide the following information:

Subnets can be used for different purposes:

• Regular subnets: This is the default subnet type. Regular subnets are created by users or automatically created in auto mode VPC networks to be used with VM instances. Regular subnets have a purpose of PRIVATE in the gcloud CLI or API. The purpose is None in the Google Cloud console.
• Private Service Connect subnets: A subnet to use to publish a managed service by using Private Service Connect.
• Proxy-only subnets: A proxy-only subnet to use with regional Envoy-based load balancers.
• Private NAT subnets: A subnet that is reserved for use as the source range for Private NAT.
• Peer migration subnets: A subnet to use to migrate a Shared VPC service to Private Service Connect.

In most cases, you cannot change the purpose of a subnet after it has been created. For more information, see the gcloud compute networks subnets update command reference.

Subnet names have the following limitations:

• Within a Google Cloud project, a subnet cannot have the same name as a VPC network unless it is a member of that network. Within a project, subnets in the same region must have unique names. For example, a network named production can have multiple subnets also named production as long as each of those subnets is in a unique region.

• You cannot change the name or region of a subnet after you create it. However, you can delete a subnet and replace it as long as no resources are using it.

Each IPv4-only or dual-stack subnet must have a primary IPv4 address range. When a subnet's purpose is PRIVATE or NONE, the primary IPv4 range can be used by the following:

• Primary internal IPv4 addresses of Compute Engine VM network interfaces, including GKE nodes.
• Alias IP ranges of VM network interfaces.
• Forwarding rules used by internal protocol forwarding.
• Forwarding rules used by internal Application Load Balancers, internal proxy Network Load Balancers, and internal passthrough Network Load Balancers.
• Cloud DNS inbound server policy entry points.
• Private Service Connect endpoints for published services.

Subnets can optionally have one or more secondary IPv4 address ranges, which can only be used by alias IP ranges. An alias IP range can come from either the primary IPv4 range or a secondary IPv4 range of a subnet.

Your IPv4 subnets don't need to form a predefined contiguous CIDR block, but you can do that if you prefer. For example, auto mode VPC networks do create subnets that fit within a predefined auto mode IP range. However, the primary range of a subnet can be 10.0.0.0/24, while the primary range of another subnet in the same network can be 192.168.0.0/16.

IPv4 subnet ranges have the following limitations:

• Each primary or secondary IPv4 range for all subnets in a VPC network must be a unique valid CIDR block.

• The number of secondary IP address ranges you can define is described in per network limits.

• After you create a subnet, the primary IPv4 range for the subnet can be expanded but not replaced or shrunk.

• You can remove and replace a subnet's secondary IPv4 address range only if no instances are using that range.

• The minimum primary or secondary range size is eight IPv4 addresses. In other words, the longest subnet mask that you can use is /29.

• The shortest subnet mask that you can use is /4. However, for most /4 IP address ranges, additional validations prevent you from creating a subnet that is this large. For example, a subnet range cannot overlap with a private IPv4 range or other reserved range. To minimize the chance of choosing an invalid subnet range, we recommend that you limit your maximum subnet size to /8.

• You can't create primary and secondary ranges for subnets that overlap with any allocated range, any primary or secondary range of another subnet in the same network, or any IPv4 ranges of subnets in peered networks. Google Cloud prevents the creation of overlapping subnet ranges in these scenarios.

• Google Cloud creates corresponding subnet routes for both primary and secondary IP ranges. Subnet routes, and therefore subnet IP ranges, must have the most specific IP ranges by definition.

  • Ensure that primary and secondary ranges don't conflict with on-premises IP ranges if you have connected your VPC network to another network with Cloud VPN, Dedicated Interconnect, or Partner Interconnect. For more information, see Check overlapping subnet ranges.

  • Subnet IPv4 ranges cannot conflict with destinations for static routes.

  • Avoid using IPv4 addresses from the 10.128.0.0/9 block for a subnet's primary or secondary IPv4 ranges. Automatically created subnets in auto mode VPC networks use IPv4 addresses from this block. If you use IP addresses in the 10.128.0.0/9 block, you cannot connect your network to an auto mode VPC network using VPC Network Peering or with Cloud VPN tunnels.

• Subnet ranges cannot match, be narrower, or be broader than a restricted range. For example, 169.0.0.0/8 is not a valid subnet range because it overlaps with the link-local range 169.254.0.0/16 (RFC 3927), which is a restricted range.

• Subnet ranges cannot span an RFC range (described in the previous table) and a privately used public IP address range. For example, 172.0.0.0/10 is not a valid subnet range because it includes both the 172.16.0.0/12 private IP address range and public IP addresses.

• Subnet ranges cannot span multiple RFC ranges. For example, 192.0.0.0/8 isn't a valid subnet range because it includes both 192.168.0.0/16 (from RFC 1918) and 192.0.0.0/24 (from RFC 6890). However, you can create two subnets with different primary ranges, one with 192.168.0.0/16 and one with 192.0.0.0/24. Or, you could use both of these ranges on the same subnet if you make one of them a secondary range.

A subnet's primary and secondary IPv4 address ranges are regional internal IPv4 addresses. The following table describes valid ranges.

Private IP addresses RFC 1918

For information about using 172.17.0.0/16, see Additional considerations.

Reserved for future use (Class E) as noted in RFC 5735 and RFC 1112.

Some operating systems don't support the use of this range, so verify that your OS supports it before creating subnets that use this range.

• Are IPv4 addresses that are normally routable on the internet, but that are used privately in a VPC network
• Cannot belong to a prohibited subnet range

When you use these addresses as subnet ranges, Google Cloud does not announce these routes to the internet and does not route traffic from the internet to them.

If you have imported public IP addresses to Google using Bring your own IP (BYOIP), your BYOIP ranges and privately used public IP address ranges in the same VPC network must not overlap.

For VPC Network Peering, subnet routes for public IP addresses are not automatically exchanged. The subnet routes are automatically exported by default, but peer networks must be explicitly configured to import them in order to use them.

Prohibited subnet ranges include Google public IP addresses and commonly reserved RFC ranges, as described in the following table. These ranges cannot be used for subnet ranges.

Google Cloud uses the first two and last two IPv4 addresses in each subnet primary IPv4 address range to host the subnet. Google Cloud lets you use all addresses in secondary IPv4 ranges.

This range is reserved by Google Cloud for potential future use.

This table lists the IPv4 ranges for the automatically created subnets in an auto mode VPC network. IP ranges for these subnets fit inside the 10.128.0.0/9 CIDR block. Auto mode VPC networks are built with one subnet per region at creation time and automatically receive new subnets in new regions. Unused portions of 10.128.0.0/9 are reserved for future Google Cloud use.

Ensure that all subnet primary and secondary IPv4 address ranges don't conflict with the IPv4 address ranges that software running within your VMs needs to use. Some Google and third-party products use 172.17.0.0/16 for routing within the guest operating system. For example, the default Docker bridge network uses this range. If you depend on a product that uses 172.17.0.0/16, don't use it as any subnet primary and secondary IPv4 address range.

When you create a subnet with an IPv6 address range or enable IPv6 on an existing subnet in a VPC network, you choose an IPv6 access type for the subnet. The IPv6 access type determines whether the subnet is configured with internal IPv6 addresses or external IPv6 addresses.

• Internal IPv6 addresses are used for VM to VM communication within VPC networks. They can only be routed within the scope of VPC networks and cannot be routed to the internet.

• External IPv6 addresses can be used for VM to VM communication within VPC networks, and are also routable on the internet.

If a VM interface is connected to a subnet that has an IPv6 subnet range, you can configure IPv6 addresses on the VM. The IPv6 access type of the subnet determines whether the VM is assigned an internal IPv6 address or an external IPv6 address.

Subnets with IPv6 address ranges are available in all regions, supporting both internal and external IPv6 subnet ranges:

• Internal IPv6 subnet ranges are always automatically assigned by Google Cloud.
  • If you want to prevent the use of a specific IPv6 address range in a VPC network, you can create an internal range resource that is associated with the IPv6 address range.
• External IPv6 subnet ranges can be assigned automatically by Google Cloud, or you can bring your own IP addresses (BYOIP).
• IPv6 subnet ranges are always /64 ranges.

Subnets with IPv6 address ranges have the following limitations:

• BYOIP-provided external IPv6 subnet ranges only support assigning /96 address ranges to VM network interfaces. IP addresses from the subnet's external IPv6 address range can't be assigned to other Google Cloud resources such as forwarding rules.

• You cannot change the IPv6 access type (internal or external) of a subnet.

• You cannot change a dual-stack subnet to IPv4 only if the IPv6 access type is internal.

• You cannot change a dual-stack or IPv4-only subnet to IPv6-only (Preview). Conversely, you cannot change an IPv6-only subnet to IPv4-only or dual-stack.

Internal IPv6 ranges are unique local addresses (ULAs). ULAs for IPv6 are analogous to RFC 1918 addresses for IPv4. ULAs cannot be reached from the internet, and are not publicly routable.

Before you can create subnets with internal IPv6 ranges, you first assign a /48 ULA IPv6 range to the VPC network. Keep the following in mind when assigning a /48 ULA IPv6 range to a VPC network:

• The /48 ULA IPv6 range for each VPC network must be unique with Google Cloud. This eliminates the possibility of overlapping IPv6 subnet ranges when using VPC Network Peering.

• You can let Google Cloud assign the VPC network's /48 ULA IPv6 range automatically, or you can provide a /48 ULA IPv6 range to use. If the /48 ULA IPv6 range you provide is already used by another Google Cloud VPC network, you receive an error.

• The option to provide a /48 ULA IPv6 range is useful to avoid conflicts between your VPC network and connected on-premises networks or networks in other cloud providers.

• After a VPC network has been assigned a /48 ULA IPv6 range, you can't remove or change the /48 ULA IPv6 range.

When you create a subnet with an internal IPv6 range, Google Cloud automatically selects an unused /64 IPv6 range from the VPC network's /48 ULA IPv6 range. Subnet internal /64 IPv6 ranges can be used by the following:

• Internal /96 IPv6 address ranges of VM network interfaces

• Internal /96 IPv6 address ranges of forwarding rules for internal protocol forwarding or internal passthrough Network Load Balancers

Internal /96 IPv6 address ranges can be assigned in the following ways:

• If not specified, Google Cloud automatically assigns an ephemeral internal IPv6 /96 address range.
• You can specify a reserved static regional internal IPv6 /96 address range.
• For VM instances, you can specify a custom ephemeral internal IPv6 /96 address range. This method isn't supported for forwarding rules.

External IPv6 address ranges are global unicast addresses (GUAs). External IPv6 addresses are available only in Premium Tier.

There are two options for creating a subnet with an external IPv6 address range:

• You can have Google Cloud automatically select an unused /64 IPv6 range from Google's regional external IPv6 addresses.

• You can assign a /64 IPv6 range from within a BYOIP sub-prefix, either specifying a particular range or letting Google Cloud select an unused range.

The resources that can use a subnet's external IPv6 address range depend on the source of the address range.

• BYOIP-provided IPv6 subnet ranges can only be used for external /96 IPv6 address ranges of VM network interfaces. You can assign IPv6 BYOIP addresses to forwarding rules, but those addresses aren't part of a subnet.

• Google-provided external IPv6 subnet ranges can be used as follows:

  • External /96 IPv6 address ranges of VM network interfaces can use the first half (/65) of the subnet's /64 range.
  • External /96 IPv6 address ranges of forwarding rules for external protocol forwarding or backend service-based external passthrough Network Load Balancers can use the second half (/65) of the subnet's /64 range.

  You must create the preceding resources using IP addresses from the corresponding /65 range allocated for the resource; otherwise, Google Cloud returns an error.

  Consider an example in which a subnet's external IPv6 address range is 2001:db8:981:4:0:0:0:0/64:

  • The /65 range allocated for use by VM instances is 2001:db8:981:4:0:0:0:0/65.
  • The /65 range allocated for use by Cloud Load Balancing is 2001:db8:981:4:8000:0.

To check the source of a subnet's external IPv6 address range, you can describe the subnet. If the ipv6AccessType property is EXTERNAL and the ipCollection property isn't empty, the subnet was created with an IPv6 BYOIP address range.

External /96 IPv6 address ranges can be assigned in the following ways:

• If not specified, Google Cloud automatically assigns an ephemeral external IPv6 /96 address range.
• You can specify a reserved static regional external IPv6 /96 address range. If you reserve a static regional external IPv6 /96 range from a BYOIP-provided IPv6 subnet range, you must specify VM for the endpoint type.
• For VM instances, you can specify a custom ephemeral external IPv6 /96 address range. This method isn't supported for forwarding rules.

IPv6 address ranges are assigned to networks, subnets, virtual machine instances (VMs), and forwarding rules.

To enable internal IPv6 on a subnet, you must first assign an internal IPv6 range on the VPC network.

A /48 ULA range from within fd20::/20 is assigned to the network. All internal IPv6 subnet ranges in the network are assigned from this /48 range.

The /48 range can be automatically assigned, or you can select a specific range from within fd20::/20.

The IPv6 access type setting controls whether the IPv6 addresses are internal or external.

A subnet can have either internal or external IPv6 addresses, but not both.

When you enable IPv6, the following occurs:

• If you enable internal IPv6 on a subnet, a /64 range of internal ULAs is assigned from your VPC network's /48 range.
• If you enable external IPv6 on a subnet, a /64 range of external GUAs is assigned in one of the following ways:
  • Google Cloud automatically assigns the range. Additionally, Google Cloud allocates each half of the /64 range for a specific purpose as follows:
    • The /65 range that represents the first half of the subnet is allocated for VM instances.
    • The /65 range that represents the second half of the subnet is allocated for Cloud Load Balancing.
  • Alternatively, you can allocate a range from a BYOIP IPv6 sub-prefix in subnet creation mode.

When you configure a dual-stack or IPv6-only network interface on a VM, the interface is assigned a /96 IP address range from the interface's subnet. Google Cloud provides the first IP address in the /96 range by using DHCPv6.

Whether a VM network interface uses an internal or external IPv6 /96 address range depends on the IPv6 access type of the interface's subnet.

The IPv6 address range of a forwarding rule for internal protocol forwarding or an internal passthrough Network Load Balancer is an internal /96 IP address range from a subnet's internal IPv6 address range. Internal /96 IP address ranges can be selected automatically by Google Cloud or you can reserve a static regional internal IPv6 /96 address range.

The IPv6 address range of a forwarding rule for external protocol forwarding or an external passthrough Network Load Balancer is one of the following:

• If using Google-provided external IPv6 addresses, the IPv6 address range is an external /96 address range selected automatically by Google Cloud from a subnet's external IPv6 address range.
• If using BYOIP external IPv6 addresses, the IPv6 address range comes from a BYOIP IPv6 address sub-prefix in forwarding rule creation mode. The size of the IPv6 range is determined by the allocatable prefix length of the sub-prefix.

The first and last /96 range of a subnet's internal /64 range cannot be specified manually because Google Cloud reserves the first and last /96 range of a subnet's internal /64 range for system use. You can manually specify any other valid /96 IPv6 range from the subnet's internal /64 range to be assigned to your VM network interfaces.

Manual specification isn't supported for external IPv6 VM network interfaces.

• Learn more about Geography and regions

• Create VPC networks

• Assign an internal IPv6 range for a VPC network

• Create a subnet

If you're new to Google Cloud, create an account to evaluate how Cloud NAT performs in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4