IOS - GRE - "tunnel protect" one end - crypto map the other
I have several IOS systems. One is functioning as the head-end for multipoint GRE tunnels with IPSEC protection using the "tunnel protection ipsec" feature in the newer releases. All of the spokes except one are running new enough code to operate the "tunnel protection ipsec" feature. .... BUT, one spoke that is due for an upgrade has to run crypto maps for now. I cannot get this node to properly negotiate with the head-end. Messages from the head-end debug are:
ISAKMP (0:2988): atts are acceptable.
IPSEC(validate_proposal_request): proposal part #1,
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...