[Openswan Users] IPsec tunnel not up with Openswan
poorvakuber at gmail.com
Wed Feb 15 11:43:33 EST 2017
Thank you for the help. I tried initiating the tunnel with the most minimum
configuration. So, here is the problem,
when I try to connect to the Cisco ASA, the source ip attached to the
packet is 10.1.10.0 instead of my public ip. And this is not recognized in
the Cisco ACL. Due to this my session is getting terminated from the remote
end. Is there any way for me to change the address associated with the
packet to be my public ip?
Here is a sample error from the Cisco ASA logs :
7|Feb 15 2017|14:27:21|713222|||||Group = <my-public-ip>, IP =
<my-public-ip>, Static Crypto Map check, map = outside_map, seq = 221, ACL
does not match proxy IDs *src:10.1.10.0* dst:<remote-subnet>
Any help in order to prevent this will be great!
On Wed, Feb 15, 2017 at 6:54 AM, John Crisp <jcrisp at safeandsoundit.co.uk>
> On 14/02/17 22:25, Poorva Kuber wrote:
> > My Openswan package was overridden by libreswan 3.15. When i remove the
> > aggressive mode, nothing changes. I get the same results that I am
> > getting when it is on.
> First, check your logs. That is what they are there for ;-)
> If you are using libreswan check out the wiki pages:
> Check left/leftnexthop in the documentation. Probably try
> leave out leftnexthop
> You can leave out ike and phase2alg and it should try all available
> encryption methods
> I'd remove as much as you can and then add options as required.
> Libreswan will connect with Openswan.
> Try something really simple like this for starters.
> config setup
> include /etc/ipsec.d/ipsec.conf
> conn Test
> Users at lists.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