Meta tags:

Headings (most frequently used words):

legacy, networks, and, about, differences, between, vpc, routes, firewall, rules, replace, what, next, single, region, conversion, tool, products, pricing, support, resources, engage,

Text of the page (most frequently used words):
the (89), network (87), vpc (60), and (58), legacy (52), google (36), #networks (36), cloud (31), for (29), overview (28), access (28), about (23), create (22), subnet (22), services (22), region (20), configure (20), resources (17), see (17), conversion (17), service (17), private (16), with (15), all (15), instances (15), manage (14), more (14), are (14), can (13), subnets (13), routes (12), single (12), information (11), add (11), you (11), use (11), published (11), converted (10), have (10), rules (10), your (10), apis (10), same (9), created (9), range (9), not (9), addresses (9), instance (8), that (8), firewall (8), tool (8), thumb (7), virtual (7), internal (7), regional (7), address (7), from (7), traffic (7), global (7), security (7), hybrid (7), other (6), stay (6), when (6), new (6), one (6), route (6), features (6), peering (6), terms (5), code (5), down (5), continue (5), reference (5), custom (5), any (5), after (5), ranges (5), using (5), only (5), vms (5), networking (5), connectivity (5), interfaces (5), português (4), español (4), support (4), policies (4), migrate (4), convert (4), existing (4), function (4), two (4), cannot (4), ipv4 (4), migrating (4), regions (4), creating (4), 240 (4), tools (4), management (4), compute (4), application (4), troubleshoot (4), policy (4), packet (4), mirroring (4), monitor (4), audit (4), logging (4), flow (4), logs (4), port (4), mapping (4), composite (4), health (4), nics (4), ipv6 (4), architecture (3), samples (3), content (3), this (3), send (3), delete (3), load (3), interface (3), will (3), newly (3), forwarding (3), during (3), converts (3), has (3), mode (3), following (3), must (3), contains (3), clusters (3), operate (3), converting (3), available (3), migration (3), multiple (3), replace (3), between (3), default (3), longer (3), based (3), guides (3), serverless (3), external (3), connections (3), routing (3), connect (3), connection (3), attachments (3), backends (3), accessing (3), profiles (3), shared (3), dynamic (3), mtu (3), prefixes (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), sign (2), site (2), youtube (2), center (2), started (2), system (2), pricing (2), products (2), understand (2), need (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), under (2), its (2), license (2), feedback (2), learn (2), what (2), balancers (2), vpn (2), tunnels (2), gateways (2), templates (2), primary (2), group (2), managers (2), implied (2), static (2), creates (2), does (2), where (2), located (2), such (2), name (2), original (2), descriptions (2), instead (2), complete (2), however (2), entire (2), gke (2), normally (2), way (2), given (2), pre (2), specific (2), move (2), individual (2), rule (2), instructions (2), start (2), note (2), divided (2), into (2), grouped (2), shown (2), example (2), spread (2), across (2), through (2), different (2), project (2), documentation (2), sdk (2), languages (2), frameworks (2), infrastructure (2), costs (2), usage (2), storage (2), observability (2), monitoring (2), industry (2), solutions (2), distributed (2), multicloud (2), databases (2), data (2), analytics (2), pipelines (2), hosting (2), development (2), advanced (2), tags (2), constraints (2), premises (2), hosts (2), update (2), view (2), failover (2), endpoints (2), own (2), rdma (2), deprovision (2), larger (2), netmasks (2), change (2), byoip (2), sub (2), public (2), alias (2), reserve (2), console (2), cross (2), product (2), technology (2), areas (2), close (2), subscribe, newsletter, our, third, decade, climate, action, join, cookies, privacy, tech, twitter, events, blog, engage, training, certification, getting, github, status, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, noted, page, details, java, registered, trademark, oracle, affiliates, developers, apache, creative, commons, attribution, how, modify, next, routers, router, nic0, referencing, also, removed, generated, called, types, automatically, didn, contain, doesn, both, isn, deleted, detail, happens, most, remain, unchanged, refer, operates, related, valid, kubernetes, engine, upgraded, ensure, components, correctly, disrupt, revert, used, because, associated, works, feature, subject, offerings, general, section, might, limited, launch, stage, preview, recreate, manually, manual, api, before, starting, including, stopped, fails, offer, gcloud, ways, want, out, user, allow, outbound, deny, inbound, outside, overall, some, each, zero, possible, differences, click, enlarge, unpredictably, figure, shows, non, internet, passes, switching, diagram, switch, then, zone, appear, ips, within, necessarily, contiguous, which, specify, scope, spans, rfc, 1918, field, deprecated, affected, ipv4range, recommended, many, newer, supported, replacing, save, categorize, preferences, organized, collections, home, concepts, topics, problems, control, partner, providers, organization, flows, records, producer, destination, overlap, dns, configuration, publish, controlling, producers, consumer, deploy, automation, backend, propagated, consumers, another, make, accessible, balanced, deployment, patterns, compatibility, choose, option, cases, disable, prepare, provision, peer, set, spokes, capabilities, netmask, additional, dns64, nat64, destinations, verify, jumbo, frame, bgp, announcement, delegated, advertised, prefix, planning, bring, get, discover, free, skip, main,

Text of the page (random words):
le cloud documentation skip to main content technology areas close ai and ml application development application hosting compute data analytics and pipelines databases distributed hybrid and multicloud industry solutions migration networking observability and monitoring security storage cross product tools close access and resources management costs and usage management infrastructure as code sdk languages frameworks and tools console english deutsch español español américa latina français indonesia italiano português português brasil עברית 中文 简体 中文 繁體 日本語 한국어 sign in virtual private cloud start free overview guides reference resources technology areas more overview guides reference resources cross product tools more console discover virtual private cloud overview get started vpc networks subnets ipv6 support create and manage vpc networks add networking features add ip addresses overview reserve internal ip addresses reserve external ip addresses move an external ipv4 address to a different project add alias ip ranges overview configure alias ip ranges bring your own ip addresses byoip overview planning and architecture create a public advertised prefix create public delegated prefixes create ipv4 sub prefixes and ip addresses create and use ipv6 sub prefixes manage bgp announcement deprovision byoip add routes routes overview static routes overview use routes add policy based routes overview use policy based routes change mtu overview change mtu of a vpc network create and verify a jumbo frame mtu network access ipv4 destinations from ipv6 only instances overview configure ipv6 only subnets and instances with dns64 and nat64 configure compute instances add network tags add vms with multiple network interfaces overview create vms with multiple network interfaces configure dynamic nics add dynamic nics delete dynamic nics configure routing for an additional network interface troubleshoot compute instance netmasks overview configure larger instance netmasks for all instances in a subnet configure a larger netmask for an instance add capabilities network connectivity center overview connect vpc networks by using vpc spokes vpc network peering overview about peering connections set up and manage vpc network peering peer two vpc networks shared vpc overview provision shared vpc deprovision shared vpc hybrid subnets about migrating to google cloud with hybrid subnets prepare for hybrid subnets connectivity migrate to google cloud with hybrid subnets disable hybrid subnet routing internal ranges overview create and use internal ranges network profiles for specific use cases overview rdma network profiles create a vpc network for rdma nics view network profiles access apis and services choose a private access option private service connect overview compatibility deployment patterns architecture security create and access your own service overview create a load balanced service make the service accessible to other vpc networks access the service from another vpc network service consumers endpoints published services about accessing published services access published services manage endpoints that access published services access published services through published service backends global google apis about accessing global google apis access global google apis regional google apis about accessing regional google apis access regional google apis about propagated connections backends about backends create a backend access published services access regional google apis access global google apis network attachments about network attachments create network attachments configure security service connection policies about service connectivity automation about service connection policies configure connectivity to services configure service connection policies deploy service instances manage consumer security service producers published services about published services about controlling access to published services publish services manage published services dns configuration for services service failover about composite health configure composite health for failover monitor composite health view update and delete composite health resources port mapping about port mapping create port mapping services update port mapping services migrate peering services to private service connect about migrating peering services migrate peering services interfaces about interfaces create interfaces configure routing configure security manage destination overlap manage producer security monitor connections private google access overview configure private google access private google access for on premises hosts overview configure private google access for on premises hosts access apis from vms with external ip addresses private services access overview configure private services access send serverless traffic to a vpc network overview configure serverless traffic monitor vpc flow logs overview about vpc flow logs records about traffic flows configure vpc flow logs configure organization policy constraints access flow logs audit logging vpc audit logging private services access audit logging serverless vpc access audit logging packet mirroring overview use packet mirroring monitor packet mirroring packet mirroring partner providers control access manage resources by using custom constraints create and manage tags for vpc resources troubleshoot troubleshoot internal connectivity between vms troubleshoot policy and access problems advanced topics advanced vpc concepts legacy networks overview manage legacy networks ai and ml application development application hosting compute data analytics and pipelines databases distributed hybrid and multicloud industry solutions migration networking observability and monitoring security storage access and resources management costs and usage management infrastructure as code sdk languages frameworks and tools home documentation networking virtual private cloud guides send feedback stay organized with collections save and categorize content based on your preferences legacy networks legacy networks are not recommended and can no longer be created many newer google cloud features are not supported in legacy networks instead use virtual private cloud vpc networks for more information see vpc networks for more information about replacing legacy networks see replace legacy networks note the ipv4range field for creating legacy networks is deprecated and is no longer available for any google cloud project you cannot create new legacy networks however existing legacy networks are not affected and continue to operate normally about legacy networks legacy networks have a single rfc 1918 range which you specify when you create the network the network is global in scope and spans all cloud regions in a legacy network instance ip addresses are not grouped by region or zone one ip address can appear in one region and the following ip address can be in a different region any given range of ips can be spread across all regions and the ip addresses of instances created within a region are not necessarily contiguous the following figure shows a legacy non vpc network traffic from the internet passes through a global switching function in the network shown in the diagram as a virtual switch then down to individual instances instances in a region can have ip addresses that are not grouped in any way as shown in the example instances from 10 240 0 0 16 are spread unpredictably across regions 1 and 2 for example 10 240 1 4 is in region 2 10 240 1 5 is in region 1 and 10 240 1 6 is in region 2 a legacy network click to enlarge differences between legacy and vpc networks legacy networks can no longer be created legacy networks have a single global ip address range that cannot be divided into subnets vpc networks are divided into subnets with vpc networks each google cloud region can have zero or more subnets it is not possible to create regional subnets with a legacy network some google cloud networking features are not available in legacy networks note you can convert a legacy network to a vpc network for more information see single region conversion tool routes legacy networks start with only two routes the default route to outside the network and the route to the overall legacy network ip range see using routes for instructions on creating routes firewall rules user created networks have a default allow all firewall rule for outbound traffic and a default deny all firewall rule for inbound traffic see use vpc firewall rules for instructions on creating firewall rules replace legacy networks if you want to move individual vm instances out of your legacy network see migrating a vm between networks if you have an existing legacy network you can replace it with a vpc network in one of two ways single region conversion tool use the gcloud or api single region conversion tool this tool converts a legacy network to a custom mode vpc network before starting the conversion all google cloud resources in the legacy network must be in a single region if the legacy network contains resources in multiple regions including stopped vms the conversion fails after the conversion the subnet in the new network has the same internal ip address range as the entire legacy network after the conversion is complete you can use all features that vpc networks offer such as creating regional subnets for more information about the conversion see converting a single region legacy network to a vpc network manual migration recreate resources in your legacy network in a vpc network for more information see manually migrating to a vpc network single region conversion tool preview this feature is subject to the pre ga offerings terms in the general service terms section of the service specific terms pre ga features are available as is and might have limited support for more information see the launch stage descriptions you can convert a legacy network to a custom mode vpc network by using the single region conversion tool during the conversion the legacy network s ip address range is used to configure a subnet in the converted vpc network because a given subnet can be associated with only one region the conversion tool works only if all resources in the legacy network are in a single region using the tool to convert from a legacy network to a vpc network does not disrupt network traffic your resources continue to operate normally the conversion is one way so you cannot revert to a legacy network after converting to a vpc network if your legacy network contains google kubernetes engine clusters your gke clusters must be upgraded after the conversion to ensure that components operate correctly for more information see converting a legacy network that contains gke clusters after the conversion is complete the new vpc network operates as any other vpc network you can add new subnets and use other vpc related features however the converted subnet has the same internal ip address range as the entire legacy network so new subnets must be created from other valid ranges the following descriptions detail what happens to resources during the conversion most resources remain unchanged and refer to the vpc subnet instead of the legacy network legacy network the legacy network isn t deleted it s converted to a vpc network the legacy network s ipv4 range is converted to the primary range of a single subnet in a vpc network vpc network google cloud converts the legacy network to a custom mode vpc network with a single subnet in the region where your vm instances are located the vpc network and subnet both have the same name as the original legacy network subnet google cloud creates a subnet and its subnet route during the conversion the subnet is created in the region where your vm instances are located google cloud automatically converts resources such as vm instances regional forwarding rules and instance group managers to the subnet the subnet has the same name as the original legacy network if the legacy network didn t contain any resources google cloud doesn t create a subnet vm instances all instances with a network interface in the converted network will reference the newly created subnet forwarding rules all internal forwarding rules in the vpc network will reference the newly created subnet routes all custom static routes stay the same when the network is converted to a vpc network if google cloud creates a new subnet it does add one system generated route called a subnet route for more information see route types firewall rules all existing firewall rules stay the same when the network is converted to a vpc network all vpc networks also have two implied firewall rules that cannot be removed for more information see implied rules instance group managers and instance templates all instance templates that have a primary network interface nic0 referencing the legacy network will reference the newly created subnet vpn tunnels and gateways vpn tunnels and gateways stay the same and continue to function when the network is converted to a vpc network cloud router cloud routers stay the same and continue to function when the network is converted to a vpc network load balancers existing load balancers stay the same and continue to function when the network is converted to a vpc network what s next to migrate convert or delete a legacy network see manage legacy networks to learn more about google cloud vpc networks see the virtual private cloud vpc overview to learn how to create and modify vpc networks see create and manage vpc networks send feedback except as otherwise noted the content of this page is licensed under the creative commons attribution 4 0 license and code samples are licensed under the apache 2 0 license for details see the google developers site policies java is a registered trademark of oracle and or its affiliates last updated 2026 07 22 utc need to tell us more easy to understand easytounderstand thumb up solved my problem solvedmyproblem thumb up other otherup thumb up hard to understand hardtounderstand thumb down incorrect information or sample code incorrectinformationorsamplecode thumb down missing the information samples i need missingtheinformationsamplesineed thumb down other otherdown thumb down last updated 2026 07 22 utc products and pricing see all products google cloud pricing google cloud marketplace contact sales support community forums support release notes system status resources github getting started with google cloud code samples cloud architecture center training and certification engage blog events x twitter google cloud on youtube google cloud tech on youtube about google privacy site terms google cloud terms manage cookies our third decade of climate action join us sign up for the google cloud newsletter subscribe english deutsch español español américa latina français indonesia italiano português português brasil עברית 中文 简体 中文 繁體 日本語 한...