지원되는 IKE 암호화에서 Cloud VPN이 여러 IKE 암호화를 지원하는 방법에 대한 세부정보를 확인할 수 있습니다.
네트워크 및 터널 라우팅에서 트래픽 선택기를 비롯한 지원되는 Virtual Private Cloud(VPC) 네트워크 및 라우팅 옵션에 대한 정보를 확인할 수 있습니다.
UDP 캡슐화
Cloud VPN은 NAT-T(NAT-Traversal)를 위해 UDP 캡슐화를 사용한 일대일 NAT만 지원합니다. IPsec 트래픽이 NAT 뒤의 외부(공개) IP 주소가 없는 대상에 도달할 수 있도록 NAT-T가 필요합니다.일대다 NAT 및 포트 기반 주소 변환은 지원되지 않습니다. 즉, Cloud VPN은 단일 외부 IP 주소를 공유하는 여러 피어 VPN 게이트웨이에 연결할 수 없습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-05(UTC)"],[],[],null,["# Advanced configurations\n\nThis page describes advanced configuration details for the following\nscenarios:\n\n- High-availability VPNs\n- High-throughput VPNs\n- Multiple subnet VPNs\n\nTo learn about the basic concepts of Cloud VPN, see the\n[Cloud VPN overview](/network-connectivity/docs/vpn/concepts/overview).\n\nOrder of routes\n---------------\n\nYou can create a VPN tunnel that has the same IP range as another tunnel,\na subset of the other tunnel's range, or a superset of the other tunnel's range.\n\nFor details, see\n[Order of routes](/network-connectivity/docs/vpn/concepts/order-of-routes).\n\nConfigure IKE, including multiple subnet support\n------------------------------------------------\n\nIn [Supported IKE ciphers](/network-connectivity/docs/vpn/concepts/supported-ike-ciphers),\nyou can find details about how Cloud VPN supports multiple\nIKE ciphers.\n\nIn [Networks and tunnel routing](/network-connectivity/docs/vpn/concepts/choosing-networks-routing),\nyou can find information about supported Virtual Private Cloud (VPC) networks\nand routing options, including traffic selectors.\n\nUDP encapsulation\n-----------------\n\nCloud VPN only supports *one-to-one NAT* by using UDP encapsulation for\nNAT-Traversal (NAT-T). NAT-T is required so that IPsec traffic can reach\ndestinations without external (public) IP addresses behind the NAT.\n*One-to-many NAT* and *port-based address translation* are\nnot supported. In other words, Cloud VPN *cannot* connect to\nmultiple [peer VPN gateways](/network-connectivity/docs/vpn/concepts/key-terms#peer-definition)\nthat share a single external IP address.\n\nFor more details about VPN gateways behind one-to-one NAT, see\n[On-premises gateways behind NAT](/network-connectivity/docs/vpn/support/troubleshooting#gateways_behind_nat)\non the Troubleshooting page.\n\nMaximum transmission unit (MTU) considerations\n----------------------------------------------\n\nThe Cloud VPN MTU size is 1460 bytes. For a description of how to\nconfigure your peer VPN gateway to support this MTU size if required, see\n[MTU considerations](/network-connectivity/docs/vpn/concepts/mtu-considerations).\n\nHigh-availability VPNs, high-throughput VPNs, and failover\n----------------------------------------------------------\n\nHA VPN is the recommended method of implementing\nhigh-availability VPNs and high-throughput VPNs. If your peer VPN gateway\nsupports BGP, you can configure an\n[HA VPN gateway with a 99.99% uptime SLA](/network-connectivity/docs/vpn/concepts/topologies#configurations_that_support_9999_availability)\nby using an\n[active/active or active/passive](/network-connectivity/docs/vpn/concepts/overview#active)\ntunnel configuration.\n| **Caution:** We recommend that you use an active/passive configuration only with *one* HA VPN gateway. If you use an active/passive configuration across *multiple HA VPN gateways*, with an active and passive tunnel pair configured on each gateway, HA VPN doesn't use the passive tunnels for failover until all the active tunnels on all gateways have failed. Configuring multiple gateways with an active/passive configuration can cause bandwidth loss.\n\nFor Classic VPN gateways, you can provide VPN redundancy\nand failover by using these\n[throughput and load balancing options](/network-connectivity/docs/vpn/concepts/classic-topologies#vpn-throughput).\nHowever, with this configuration, you receive a 99.9% availability SLA.\n\nWhat's next\n-----------\n\n- To learn about the basic concepts of Cloud VPN, see the [Cloud VPN overview](/network-connectivity/docs/vpn/concepts/overview).\n- To help you solve common issues that you might encounter when using Cloud VPN, see [Troubleshooting](/network-connectivity/docs/vpn/support/troubleshooting)."]]
