Amazon Virtual Private Cloud
网络管理员指南
AWS 服务或AWS文档中描述的功能,可能因地区/位置而异。点 击 Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.

示例:Dell SonicWALL 设备

本主题提供一个示例,说明当客户网关是 Dell SonicWALL 路由器时如何配置路由器。

本节假定已在 Amazon VPC 控制台中配置了一个具有静态路由的 VPN 连接。有关更多信息,请参阅 Amazon VPC 用户指南 中的在您的 VPC 中添加硬件虚拟专用网关

客户网关的宏观视图

下面的示意图显示您的客户网关的详细信息。请注意 VPN 连接包含两个隧道:Tunnel 1Tunnel 2。使用冗余隧道确保某个设备发生故障情况下的持续可用性。

 客户网关概要示意图

示例配置文件

从 Amazon VPC 控制台下载的配置文件包含所需的值,以便您使用 OS 6.2 上的命令行工具配置 SonicWALL 设备的每个隧道及 IKE 和 IPsec 设置。

重要

以下配置信息使用示例值 - 您必须使用实际值,而不是此处显示的示例值,否则您的实现将失败。

Copy
! Amazon Web Services ! Virtual Private Cloud ! ! VPN Connection Configuration ! ================================================================================ ! AWS utilizes unique identifiers to manipulate the configuration of ! a VPN Connection. Each VPN Connection is assigned a VPN Connection Identifier ! and is associated with two other identifiers, namely the ! Customer Gateway Identifier and the Virtual Private Gateway Identifier. ! ! Your VPN Connection ID : vpn-44a8938f ! Your Virtual Private Gateway ID : vgw-8db04f81 ! Your Customer Gateway ID : cgw-ff628496 ! ! This configuration consists of two tunnels. Both tunnels must be ! configured on your Customer Gateway. ! ! This configuration was tested on a SonicWALL TZ 600 running OS 6.2.5.1-26n ! ! You may need to populate these values throughout the config based on your setup: ! <vpc_subnet> - VPC address range ! ! IPSec Tunnel !1 ! ================================================================================ ! #1: Internet Key Exchange (IKE) Configuration ! ! Please note, these sample configurations are for the minimum requirement of AES128, SHA1, and DH Group 2. ! You can modify these sample configuration files to use AES128, SHA1, AES256, SHA256, or other DH groups like 2, 14-18, 22, 23, and 24. ! The address of the external interface for your customer gateway must be a static address. ! Your customer gateway may reside behind a device performing network address translation (NAT). ! To ensure that NAT traversal (NAT-T) can function, you must adjust your firewall rules to unblock UDP port 4500. If not behind NAT, we recommend disabling NAT-T. ! config address-object ipv4 AWSVPC network 172.30.0.0/16 vpn policy tunnel-interface vpn-44a8938f-1 gateway primary 72.21.209.193 bound-to interface X1 auth-method shared-secret shared-secret PRE-SHARED-KEY-IN-PLAIN-TEXT ike-id local ip your_customer_gateway_IP_address ike-id peer ip 72.21.209.193 end ! ! #2: IPSec Configuration ! ! The IPSec (Phase 2) proposal defines the protocol, authentication, ! encryption, and lifetime parameters for our IPSec security association. ! Please note, you may use these additionally supported IPSec parameters for encryption like AES256 and other DH groups like 2, 5, 14-18, 22, 23, and 24. ! config proposal ipsec lifetime 3600 proposal ipsec authentication sha1 proposal ipsec encryption aes128 proposal ipsec perfect-forward-secrecy dh-group 2 proposal ipsec protocol ESP keep-alive enable commit end ! ! ! You can use other supported IPSec parameters for encryption such as AES256, and other DH groups such as 2, 5, 14-18, 22, 23, and 24. ! IPSec Dead Peer Detection (DPD) will be enabled on the AWS Endpoint. We ! recommend configuring DPD on your endpoint as follows: - DPD Interval : 120 - DPD Retries : 3 ! To configure Dead Peer Detection for the SonicWall device, use the SonicOS management interface. ! ! #3: Tunnel Interface Configuration ! ! The tunnel interface is configured with the internal IP address. ! ! To establish connectivity between your internal network and the VPC, you ! must have an interface facing your internal network in the "Trust" zone. ! config tunnel-interface vpn T1 ip-assignment VPN static ip 169.254.44.242 netmask 255.255.255.252 ! ! ! #4: Border Gateway Protocol (BGP) Configuration: ! ! BGP is used within the tunnel to exchange prefixes between the ! Virtual Private Gateway and your Customer Gateway. The Virtual Private Gateway ! will announce the prefix corresponding to your VPC. ! ! ! The local BGP Autonomous System Number (ASN) (65000) ! is configured as part of your Customer Gateway. If the ASN must ! be changed, the Customer Gateway and VPN Connection will need to be recreated with AWS. ! routing bgp configure terminal router bgp YOUR_BGP_ASN network <Local_subnet>/24 neighbor 169.254.44.242 remote-as 7224 neighbor 169.254.44.242 timers 10 30 neighbor 169.254.44.242 soft-reconfiguration inbound end exit commit end ! ! IPSec Tunnel #2 ! -------------------------------------------------------------------------------- ! #1: Internet Key Exchange (IKE) Configuration ! ! Please note, these sample configurations are for the minimum requirement of AES128, SHA1, and DH Group 2. ! You can modify these sample configuration files to use AES128, SHA1, AES256, SHA256, or other DH groups like 2, 14-18, 22, 23, and 24. ! The address of the external interface for your customer gateway must be a static address. ! Your customer gateway may reside behind a device performing network address translation (NAT). ! To ensure that NAT traversal (NAT-T) can function, you must adjust your firewall rules to unblock UDP port 4500. If not behind NAT, we recommend disabling NAT-T. ! config address-object ipv4 AWSVPC network 172.30.0.0/16 vpn policy tunnel-interface vpn-44a8938f-1 gateway primary 72.21.209.225 bound-to interface X1 auth-method shared-secret shared-secret PRE-SHARED-KEY-IN-PLAIN-TEXT ike-id local ip your_customer_gateway_IP_address ike-id peer ip 72.21.209.225 end ! ! #2: IPSec Configuration ! ! The IPSec (Phase 2) proposal defines the protocol, authentication, ! encryption, and lifetime parameters for our IPSec security association. ! Please note, you may use these additionally supported IPSec parameters for encryption like AES256 and other DH groups like 2, 5, 14-18, 22, 23, and 24. ! config proposal ipsec lifetime 3600 proposal ipsec authentication sha1 proposal ipsec encryption aes128 proposal ipsec perfect-forward-secrecy dh-group 2 proposal ipsec protocol ESP keep-alive enable commit end ! ! ! You can use other supported IPSec parameters for encryption such as AES256, and other DH groups such as 2, 5, 14-18, 22, 23, and 24. ! IPSec Dead Peer Detection (DPD) will be enabled on the AWS Endpoint. We ! recommend configuring DPD on your endpoint as follows: - DPD Interval : 120 - DPD Retries : 3 ! To configure Dead Peer Detection for the SonicWall device, use the SonicOS management interface. ! ! #3: Tunnel Interface Configuration ! ! The tunnel interface is configured with the internal IP address. ! ! To establish connectivity between your internal network and the VPC, you ! must have an interface facing your internal network in the "Trust" zone. ! config tunnel-interface vpn T2 ip-assignment VPN static ip 169.254.44.114 netmask 255.255.255.252 ! ! #4: Border Gateway Protocol (BGP) Configuration: ! ! BGP is used within the tunnel to exchange prefixes between the ! Virtual Private Gateway and your Customer Gateway. The Virtual Private Gateway ! will announce the prefix corresponding to your VPC. ! ! The local BGP Autonomous System Number (ASN) (65000) ! is configured as part of your Customer Gateway. If the ASN must ! be changed, the Customer Gateway and VPN Connection will need to be recreated with AWS. ! routing bgp configure terminal router bgp YOUR_BGP_ASN network <Local_subnet>/24 neighbor 169.254.44.114 remote-as 7224 neighbor 169.254.44.114 timers 10 30 neighbor 169.254.44.114 soft-reconfiguration inbound end exit commit end

使用管理界面配置 SonicWALL 设备

您还可以使用 SonicOS 管理界面配置 SonicWALL 设备。有关更多信息,请参阅 使用管理界面配置 SonicWALL 设备

您无法使用管理接口配置此设备的 BGP。请使用上述示例配置文件中名为 BGP 的部分中提供的命令行指令进行配置。

如何测试客户网关配置

您可以测试每条隧道的网关配置。

如需测试每条隧道的客户网关配置

  1. 在客户网关上确定 BGP 状态是 Active

    BGP 对等体变为活跃状态约需 30 秒。

  2. 确保客户网关在向虚拟专用网关发布路由。路由可以是默认路由 (0.0.0.0/0),也可以是您选择的更具体的路由。

正确建立后,您的 BGP 对等体应该从虚拟专用网关接收一条路由,该网关对应您的 VPC 整合团队为该 VPC 指定的前缀(例如 10.0.0.0/24)。如果 BGP 对等体已建立并且您正在接收和发布前缀,那么您的隧道就已正确配置。请确保两条隧道均处于该状态。

然后,您必须测试每个隧道的连接性,方法是在您的 VPC 中启动一个实例,从您的家庭网络 Ping 该实例。在您开始之前,确保完成以下操作:

  • 使用可以响应 Ping 请求的 AMI。我们建议您使用 Amazon Linux AMI 之一。

  • 配置实例的安全组和网络 ACL,以启用入站 ICMP 流量。

  • 确保已配置 VPN 连接路由:您的子网路由表必须包含到虚拟专用网关的路由。有关更多信息,请参阅Amazon VPC 用户指南中的在路由表中启用路由传播

如需测试各条隧道的端到端连接性

  1. 请将 Amazon Linux AMI 的任一实例启动到您的 VPC。当您从 Amazon EC2 控制台中启动实例时,在启动向导中将会列出 Amazon Linux AMI。有关更多信息,请参阅 Amazon VPC 入门指南

  2. 当实例开始运行后,获取其私有 IP 地址(例如 10.0.0.4)。 控制台显示的地址是实例详细信息的一部分。

  3. 在您的本地网络中的系统上,对实例的 IP 地址使用 ping 命令。确保您发出 ping 的计算机位于客户网关后。成功的响应内容应类似如下所示。

    Copy
    ping 10.0.0.4
    Pinging 10.0.0.4 with 32 bytes of data:
    
    Reply from 10.0.0.4: bytes=32 time<1ms TTL=128
    Reply from 10.0.0.4: bytes=32 time<1ms TTL=128
    Reply from 10.0.0.4: bytes=32 time<1ms TTL=128
    
    Ping statistics for 10.0.0.4:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
    
    Approximate round trip times in milliseconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

    注意

    如果您从客户网关路由器向实例发出 ping,请确保您的 ping 消息信源为内部 IP 地址,而非隧道 IP 地址。部分 AMI 不响应从隧道 IP 地址发出的 ping 消息。

  4. (可选) 为测试隧道故障转移,您可临时禁用您的客户网关上的一个隧道,然后重复上一步。您无法禁用 VPN 连接的 AWS 端的隧道。

如果您的隧道测试不成功,请参阅 排查使用边界网关协议的通用设备客户网关连接性问题