- 最新
- 投票最多
- 评论最多
Hello,
Think of the Client CIDR Block as the Pool of IPs that are handed out to every client that connects to the CVPN. ClientVPN actually does a Source NAT when you connect to the destination.
For example, if you expect to support 8,000 VPN connections to your Client VPN endpoint, specify a minimum client CIDR range size of /18 (16,384 IP addresses), and associate at least 2 subnets with the Client VPN endpoint.
If you’re unsure what the number of expected VPN connections is for your Client VPN endpoint, we recommend that you specify a size /16 CIDR block or larger.
On the other hand note that you can associate the client VPN endpoint to multiple subnets. The requirement is that each of the subnets needs to belong to the same VPC but different Availability Zones
@Tushar_J Thanks for the response. So given these parameters:
Private Subnet: 10.100.1.0/24
Client CIDR Block: 10.0.0.0/22
Client Network Association: 10.100.0.0/27
Test VPN Address: 10.0.0.6
Test Private Network: 10.100.2.0/24
I'm trying to ping an EC2 instance on my Test Private Network from my Test VPN Address. Here's where I still don't understand:
Test Private Network ACL Allow: [Client CIDR Block] - will not allow access
Test Private Network ACL Allow: [Client Network Association CIDR Block] - will allow access
I'm guessing there is some type of Private IP NAT going on at the Client Network Association?
But I'm confused as to why the NACL works for my Client Network Association CIDR Block and not my Client CIDR block.
Thanks,
Joe
相关内容
AWS 官方已更新 7 个月前- AWS 官方已更新 2 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 9 个月前
Hi Joe, yes that is correct. When traffic from the end user device reaches the Client VPN endpoint, the source IP address of the packets is translated to the Client VPN endpoint network interface's IP address using source NAT. As a result, the target resources have visibility into all the traffic that's sourced with the Client VPN endpoint network interface's IP address.