- 最新
- 最多得票
- 最多評論
I suggest you check the following:
-
Make sure you're using route-based VPN and not policy-based VPN, if you're using policy-based VPN then make sure you're only defining one CIDR on the pfsense as the proxy ID, defining two CIDRs will cause multiple security associations and that would cause connectivity issue. Refer to [1].
-
If you're using static VPN, make sure you enable asymmetric routing on the pfsense, if you don't want to enable the asymmetric routing on the pfsense, then disable one of the tunnels and have only one tunnel up and test the connectivity. This is to roll out the asymmetric routing issue. Refer to [2].
-
Make sure the traffic is being allowed in the NACL.
-
If the above does not resolve the issue, I suggest enabling VPC flow logs and see if the traffic is being received by the EC2 from on-prem. Refer to [3].
-
Make sure you have a proper static route on the AWS VPN side for your on-prem network 10.1.10.0/26. Refer to [4].
References:
相關內容
- 已提問 6 個月前
- 已提問 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 6 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
Thank You, I figured it out. I forgot to add a rule to the pfsense wan interface to allow access to the my aws subnet.