We use “alias” commands in our ASA configuration that were migrated from our PIX. The presence of these commands precludes the use of the configuration functions within the appliance’s Device Manager application. I have done some research on replacing/rewriting the lines to use the outside NAT function, but I’m still not clear on it. Could someone please give me an example (using just one alias statement) of the syntax changes would be necessary to update the config in order to fully utilize ASDM? TIA
Re: Using outside NAT statements to replace "alias"
My understanding was that you replaced the alias command by adding the "dns" tag in your static command. This does not work for me. So do I create a seperate static command with the global and local ip reversed, using the "dns" tag in this command in order for this to work?
For example, if I have a server on my inside network, www.domain.com, which has the IP address 10.1.1.1, but is world-resolvable to 184.108.40.206, I would have used alias like this:
alias (inside) 220.127.116.11 10.1.1.1 255.255.255.255
However, if I use the static command instead, then would I have to have both of these?
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...