I'm able to get the tunnel to establish but am getting the following error:
4 Sep 17 2007 03:31:32 402116 220.127.116.11 18.104.22.168 IPSEC: Received an ESP packet (SPI= 0x57FB960B, sequence number= 0x25) from 22.214.171.124 (user= 126.96.36.199) to 188.8.131.52. The decapsulated inner packet doesn't match the negotiated policy in the SA. The packet specifies its destination as 184.108.40.206, its source as 220.127.116.11, 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?
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.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...