たとえば、OpenVPN Access Server は VPN ゲートウェイのマーケットプレイス ソリューションです。アプライアンスをアクティブにした後、VMware Engine ネットワークへの移行を可能にするゲートウェイのホスト VM をデプロイします。
OpenVPN Access Server 管理者パネルで暗号化ドメインの設定にアクセスするには、[構成] > [VPN 設定] > [ルーティング] に移動します。次に、[Specify the private subnets to which all clients should be given access] というラベルのフィールドに、サブネット IP アドレス範囲のリストを入力します。
[[["わかりやすい","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-04-22 UTC。"],[],[],null,["# VPN gateways\n============\n\nVPN gateways provide secure connectivity between multiple sites, such as\non-premises data centers, Google Cloud Virtual Private Cloud (VPC) networks,\nand Google Cloud VMware Engine private clouds. Traffic is encrypted because the VPN\nconnections traverse the internet. Each VPN gateway can support multiple\nconnections. When you create multiple connections to the same VPN gateway, all\nVPN tunnels share the available gateway bandwidth.\n\nVMware Engine supports VPN connectivity by using the following types\nof gateways:\n\n- **Point-to-site VPN gateways:** for point-to-site connections, like connecting from your computer to your private cloud\n- **[Cloud VPN](/network-connectivity/docs/vpn) or [Cloud Interconnect](/network-connectivity/docs/interconnect):** for site-to-site connections, like establishing a connection between your on-premises network and your private cloud\n\nFor more details about Cloud VPN and Cloud Interconnect, see\n[Choosing a Network Connectivity product](/network-connectivity/docs/how-to/choose-product).\n\nPoint-to-site VPN gateways\n--------------------------\n\nA point-to-site VPN gateway sends encrypted traffic between a\nVMware Engine network and a client computer. You can use a VPN\ngateway to access your private cloud network, including your private cloud\nvCenter and workload VMs. To connect to your private cloud after you set up your\nVPN gateway, see [Connecting using VPN](/vmware-engine/docs/networking/howto-vpn-connect).\n\nTo set up a point-to-site VPN gateway, first choose a marketplace vendor\nsolution. You can deploy marketplace VPN gateway solutions as VMs on a\nVPC network connected to your private cloud. Alternatively, you\ncan deploy VPN gateway VMs in VMware Engine, then expose and secure\nthem using the VMware Engine public IP service and external firewall\nrules.\n\nAfter you set up the VPN gateway, extend the encryption domain to include both\nthe management and NSX subnets in your private cloud. If preferred, you can\nsummarize or group subnets when setting up your encryption domain.\n\nTo get a list of the subnets to add to your encryption domain, do the following:\n\n1. [Access the Google Cloud console](https://console.cloud.google.com/vmwareengine).\n2. From the main menu, go to **Subnets**.\n3. From the **Subnet** column, copy the IP address ranges that you want to get access to remotely.\n\n### Example: OpenVPN Access Server\n\nFor example, [OpenVPN Access Server](https://openvpn.net/vpn-server-resources/google-cloud-platform-byol-instance-quick-launch-guide/) is a\nmarketplace solution for a VPN gateway. After you activate the appliance, you\ndeploy a host VM for the gateway that allows transit to VMware Engine\nnetworks.\n\nTo access the encryption domain settings in the OpenVPN Access Server administrator\npanel, go to **Configuration \\\u003e VPN Settings \\\u003e Routing**.\nThen, enter a list of your subnet IP address ranges in the field labeled\n\"Specify the private subnets to which all clients should be given access\"."]]
