Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Weird IPsec L2L problem

I'm getting the error message in my syslog showing the remote user is going after 0.0.0.0 even though the decrypted packet is showing 10.200.130.x

11-16-2007 10:42:53 Local4.Warning 10.200.x.x Nov 16 2007 10:42:53 BHG-FW : %ASA-4-402116: IPSEC: Received an ESP packet (SPI= 0xC3FABF97, sequence number= 0x2) from 207.59.x.x (user= 207.59.x.x) to Outside_PAT. The decapsulated inner packet doesn't match the negotiated policy in the SA. The packet specifies its destination as 10.200.x.x, its source as 207.59.x.x, and its protocol as 6. The SA specifies its local proxy as 0.0.0.0/255.255.255.255/0/0 and its remote_proxy as 207.59.x.x/255.255.255.255/0/0.

Any ideas what is going on here? I only get this far if I put the local network as any, if I specify the 3 hosts that I only want to allow access to nothing works.

1 REPLY
New Member

Re: Weird IPsec L2L problem

Do your ACL's at each end match exactly?

268
Views
0
Helpful
1
Replies