[Openswan Users] Openswan on EC2 - Resolving IP confusions
raohammad at gmail.com
Fri Dec 24 03:49:54 EST 2010
>> Secondly, I have tried to route traffic to 220.127.116.11(remote encyrpted
domain IP) through my virtual interface(local encrypted domain IP) 10.5.5.5.
Still its no use.
by adding route add -host 18.104.22.168 gw 10.5.5.5 manually;
On Fri, Dec 24, 2010 at 1:44 PM, Hammad <raohammad at gmail.com> wrote:
> 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
> 22.214.171.124(remote encyrpted domain IP) through my virtual interface(local
> encrypted domain IP) 10.5.5.5. 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 *10.5.5.5* netmask 255.255.255.255 broadcast 10.5.5.255
>> > I have already used this scheme with OpenSWAN and virtual interface
>> > this way. But in that case, my public IP was on interface eth0. But here
>> > EC2, I see a new IP 10.254.254.254...
>> That's a private IP address. You seem to have a NAT device in there. Have
>> taken the necessary steps to 'work around' the NAT? Or are you expecting
>> use a publicly routable IP address?
>> Users at openswan.org
>> Micropayments: https://flattr.com/thing/38387/IPsec-for-Linux-made-easy
>> Building and Integrating Virtual Private Networks with Openswan:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users