an EZVPN Client does not properly disconnect its tunnel to a VPN3000 Concentrator, its IKE SA is not cleared from the Concentrator. The result is that each lingering IKE SA retains an address out of the address pool.
This occurs only if the Client connects without xauth authentication.
Many "IPSEC ESP bad pad length (8) >= buffer length (8)" messages were logged in a syslog.
Using VPN3000 and PIX EzVPN:
Phase 2 SA recreation after an expiration of a SA because of an idle timeout (30min)
35 sec after a creation of a new SA after an old SA lifetime Expiration
Thanks for your answer. I solved this problem doing some lab tests. I think Cisco's doc. about EzVPN (VPN300-to-IOS) is not complete. I had to "Allow Network Extension Mode" and "Store password on HW Client" in order to make this solution to work. My idea from the beginning was to have a EzVPN like a LAN-to-LAN solution. Now i have it up and running.
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...