sai karthik thati
I am trying to establish a site-to-site ipsec connectivity between my network and AWS. I installed openvpn access server in one of the machines that is acting as Customer Gateway. I downloaded the generic VPN configuration file and configured openvpn access server's ipsec.conf and ipsec.secrets file and the 2 tunnels in AWS VPN are UP. But the problem is that I am unable to ping either ways (from an ec2 machine to a machine in my local network subnet and vice versa). Also note that I am using static routes to setup the AWS VPN Connection.
Steps I followed to setup my openvpn access server after downloading the vpn configuration file.
-> Edited ipsec.conf file with
rightsubnet=192.168.0.0/16 ==> vpc CIDR
conn VPC-CUST-GW1
right=VPG-1-outside-IP-Addr
conn VPC-CUST-GW2
right=VPC-1-outside-IP-Addr
->Edited ipsec.secrets file with pre-shared keys
->Restarted ipsec and the VPN tunnels in AWS are UP.
There are 4 additional interfaces in openvpn access server with inet-addr from 172.27.224.0/20. I do not see any tunnel in openvpn access server that shows connection to AWS Virtual Gateway. I am not sure whether it shows one.
AWS side
->launched and ec2-instance in the public subnet.
->As of now for testing, the inbound and outbound security group rules are having All traffic open.
->Route propagation is enabled for the public subnet.
->static routes in AWS are configured to route both subnet-cidr of my local network and OpenVPN-VPN-IP-CIDR (172.27.224.0/20) through virutal gateway.
I connected to this openvpn access server with another machine in the same local network using openvpn client and tried to ping to the ec2-instance -private-ip but not able to receive back any packets.
I also tried adding a static route in openvpn access server as
ip route add virtural-gateway-1-private-ip via 172.27.236.1
ip route add virtural-gateway-2-private-ip via 172.27.236.1
I used 172.27.236.1 because the client is connected to the 4th interface.
Any help in this would be greatly appreciated.
