I am facing a problem trying to establish a tunnel with one of our supplier.
Their side is terminated on a IOS router currently unknown type and version (should be 12.2 - 12.4), my side is an ASA 7.2(2), configurations are attached (at least the snippet of the IOS config I was sent).
Apparently Phase 1 completes correctly but P2 fails with "Received non-routine Notify message: No proposal chosen (14)", I also attach debug from ASA with " debug crypto isakmp 129" and "debug crypto ipsec 129".
I double checked transform sets and IKE policies.
BTW I never had to use static NAT AND IPSec as here (I was asked to do so by other side), I have found few config examples on that (to solve overlapping networks), I hope it is possible with ASA o.s. too.
parameters that takes default values don't show up in "show running-config" so that's why you can't find DH Group and encryption in the IOS ISAKMP policy, anyway they matched.
BTW exactly last Friday 22/06 we found what was blocking P2 to complete.
On the IOS router they have stated:
crypto map MAPNAME local-address Loopback0
which I understand use the Loopback0 address as identity in IPSec SA, too bad in some other place of the configuration they never showed me they put:
no ip address
That, without any experience, sounded very strange to me so I asked them to remove the former statement (crypto map .... local-address) and voila' IPSec SA ok and VPN traffic flowing, of course using the physical interfaces IP address as IPSec identities.
It remains the question of why other (IOS based) peers were working correctly (and still are!) with that router totally unregarding the guilty piece of config....
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...