I'm playing a bit with an ASA and I came across a silly problem. For some reason there is an implicit ACL that prevents me from connect to tcp port 443 on the ASA hence no asdm.
Does anybody ever had the same issue?
I'm trying to find where to configure this access-list but since only one interface is configured and given the fact that the acl applied to that interface is permit any any I really wonder when the other ACL is applied...
I first configured the http server to listen to some dummy tcp port instead of 443 then revert it back to 443 but for some reason the change did not take effect. I had te disable / enabel the http server in order to have it working.
I guess the implicit access-list message was related to the fact that only the configured port for the http server is allowed on the ASA, by default 443, but when you change it...
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...