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?

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.

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠