[Openswan Users] Openswan on EC2 - Resolving IP confusions

Hammad raohammad at gmail.com
Fri Dec 24 03:44:37 EST 2010

in ipsec.conf; nat_traversal=yes; I think there is nothin more than this in
provisioning openswan for NAT. Secondly, I have tried to route traffic to encyrpted domain IP) through my virtual interface(local
encrypted domain IP) Still its no use.

I have enabled /etc/sysctl.conf -> net.ipv4.ip_forward = 1

what else?

Here is quite a disappointing post; but we cant let openswan die in EC2
environment so it should be resolved.


On Fri, Dec 24, 2010 at 4:13 AM, Neal Murphy <neal.p.murphy at alum.wpi.edu>wrote:

> On Thursday 23 December 2010 13:38:40 Hammad wrote:
> > Hi Piavlo,
> >
> > Its a virtual interface. I created with;
> >
> > ifconfig eth0:0 ** netmask broadcast
> >
> > I have already used this scheme with OpenSWAN and virtual interface
> created
> > this way. But in that case, my public IP was on interface eth0. But here
> on
> > EC2, I see a new IP
> That's a private IP address. You seem to have a NAT device in there. Have
> you
> taken the necessary steps to 'work around' the NAT? Or are you expecting to
> use a publicly routable IP address?
> N
> _______________________________________________
> Users at openswan.org
> http://lists.openswan.org/mailman/listinfo/users
> Micropayments: https://flattr.com/thing/38387/IPsec-for-Linux-made-easy
> Building and Integrating Virtual Private Networks with Openswan:
> http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openswan.org/pipermail/users/attachments/20101224/aee78afb/attachment.html 

More information about the Users mailing list