1 回答
- 最新
- 投票最多
- 评论最多
0
Hello.
If there are no problems with the EC2 security group or subnet network ACL settings, I think there may be a routing problem.
Is there a communication route to the on-premises set in the subnet route table?
If it is set statically, please manually set the communication route in the route table.
https://docs.aws.amazon.com/vpn/latest/s2svpn/VPNRoutingTypes.html
If you are using BGP, try enabling propagated in your route table.
https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html#vpn-configure-route-tables
Will it be successful if I set the IP address restriction for ICMP communication to 0.0.0.0/0 etc. in the EC2 security group?
If it succeeds, there is a problem with the IP address range set in the security group.
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 7 个月前
- AWS 官方已更新 2 年前
I do have communication route to the On-Premises set int he subnet route table. Propagation is set for the virtual private gateway under the Route propagation tab.