I installed the patch successfully, but am unable to get past 4.1(5)S189. It does nothing - I've checked disk space and rebooted the sensor but it just won't take and now I'm going to try the latest and greatest sigs, but I'm pretty certain that those won't take either.
The 4.1(5) completed absolutely perfectly - no notifications, smooth as glass. Which is why I don't understand why subsequent signature updates aren't going in.
Since I'm not exactly getting a plethora of responses, I'm going to assume this isn't a wide-spread known issue. I was hoping for a "hey, that happened to me and this is what I did." Looks like TAC is my best option?
Thats funny, I had the exact opposite happen to me. I recovered a sensor back to 4.1.1S47, upgraded on the sensor from an FTP server to sp4.1-5S189, but was unable to upgrade to sig-4.1-5S200 or 201 on the sensor. I was able to apply the sig update via VMS.
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...