I am not sure. That firewall was not configured by me originally. I am new to this organization and the network engineer left so nobody has a clue. I am just attempting to replace all the comfigs as they were. You are right I see the configs exactly were you told me they would be. Thanks for your help Jon.
Oh yeah the to statement at the bottom would not work in the ASA either. Do you know why?
won't work because the ASA doesn't use conduits. The equivalent is just an access-list ie.
access-list icmptraffic permit icmp any any
but you need to work out where it has been applied.
"pdm history enable"
won't work because the ASA uses ASDM not PDM.
I wouldn't worry about the fixups, they always appear in the config and a lot of the time there is no need to modify them so you just accept the defaults so you can do the same on the ASA. If something that relies on a fixup stops working that would be the time to worry :-).
As for the ICMP - not sure how this was applied on your previous pix.
The issue is that you have a 5505 with a basic license. And that basic license puts restrictions on the use of the third VLAN. I believe that if you add the no forward command to the interface then you will be able to name 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...