Perfect! That was the problem. Thanks. One more question about this.
The document says that "All events except 1 occur when a dynamic crypto map is used without a match address statement." Since I am using a match address statement, does this mean that this issue should only impact me if I remove and reapply the crypto-map and/or isakmp statement on the pix?
And yes, your interpretation of the bug description seems to be correct to me. Well, to be a little bit more precise: the problem occurs if at some point in time there is GRE traffic but no crypto map or a crypto map without match on GRE.
So once you have the match statement in there, it will only affect you when you remove and reapply the crypto map, or if you remove and re-add the match statement.
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...
[toc:faq]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 and UDP are I...