Why cant I route through a VM

0

I have a working fortinet AWSmarketplace VM, that can route packets through a VPN. I'm trying to set up a second VM, with a different VPN solution.

So, I'm trying to ping 10.1.1.1 I have a test VM in the same AWS subnet. I force a route for 10.1.1.1 through the first (fortinet) VM, set up packet capture, and do a test ping. packet capture shows that it sees the ping packets.

I change the route to point to the new VM. I copied the security group used by fortinet VM, to the new VM. Set up packet capture via tcpdump. packet capture shows if I ping the VM itself. But when I try to ping 10.1.1.1... nothing.

What am I missing here??

I know that GCP has a special magical "let this VM route packets" setting for its VMs that is needed in this type of situation. but I havent found anything like that for AWS. Is it hiding somewhere unexpected?

pbrown
已提問 2 個月前檢視次數 374 次
1 個回答
1
已接受的答案

You must disable the source/destination check on the ENI. See https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html

profile pictureAWS
已回答 2 個月前
profile picture
專家
已審閱 2 個月前
profile picture
專家
已審閱 2 個月前
  • Thank you so much! That was it.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南