Iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE Some configuration: VPC Subnet: 10.10.1.0/24 ![]() My first thought was that it was related to the EC2 instance only having a single network interface, however I have setup a OpenVPN connections before without a problem, though they usually make use of a tunnel device and I haven't really found an example of openswan with a tunnel or a single interface. I can run tcpdump and see the ping requests show up, however they never make it to the other host. I can't talk to anything else on the network. So far, I have it setup to where I can successfully connect to the openswan server running in VPC, however I can only ping the openswan server's internal IP. We already use it to connect to our existing networks through hardware based VPNs and were hoping to just continue using it to connect to our VPC network. Our VPN client of choice is Equinux VPN Tracker ( ) for Mac OS X. The goal is to make it so we can VPN into VPC and have our workstations be as if they were on the network, more of a roadwarrior configuration. ![]() ![]() Trying to set up a openswan based server sitting in an Amazon VPC cluster.
0 Comments
Leave a Reply. |