VPN between ASA 5510 and Netscreen

Unanswered Question
Sep 16th, 2007

I'm able to get the tunnel to establish but am getting the following error:

4 Sep 17 2007 03:31:32 402116 221.133.224.70 216.115.176.14 IPSEC: Received an ESP packet (SPI= 0x57FB960B, sequence number= 0x25) from 221.133.224.70 (user= 221.133.224.70) to 216.115.176.14. The decapsulated inner packet doesn't match the negotiated policy in the SA. The packet specifies its destination as 216.115.176.14, its source as 221.133.224.70, and its protocol as 1. The SA specifies its local proxy as 10.2.0.0/255.255.0.0/0/0 and its remote_proxy as 172.16.32.0/255.255.255.0/0/0.

I can ping from the Cisco side to the Netscreen side, but in the reverse. The Netscreen reports the tunnel being inactive.

Are there any interoperability issue here? What can I do to make this work?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jon Marshall Sun, 09/16/2007 - 23:56

Hi Anthony

From the above message it looks like you have setup the VPN with a local subnet of 10.2.0.0/16 and a remote subnet of 172.16.32.0/24.

But the source and destination IP addresses on the packet that has been encrypted are not part of these subnets. This may well be because you are initiating packets off the firewall itself. You could either

1) Try a connection from a client behind your firewall

2) Add in the public IP addresses 221.133.x.x etc. to your crypto map access-list to allow the traffic.

Jon

Actions

This Discussion