When I enter a rule on the firewall via CLI such as:
access-list dmz-in permit tcp any host 10.10.10.100 eq tcp
access-group dmz-in in interface dmz
I look at PDM and the rule is marked "null rule". If I edit the rule in PDM, the destination and source hosts are incorrect.
If I change them to be "outside" and "DMZ", and click apply, I get a message that "Access rules on PIX are grouped by and applied to the incoming (source) interface. The new rule you specified has a different incoming interface than the rule you selected as the reference point before or after which the new rule is to be inserted."
The PIX has a large access-list applied to the outside interface allowing traffic to the inside. If I simply add a rule in PDM that allows traffic from the outside to the DMZ interface, it gets added to this access list, which is not applied to the DMZ interface.
Anyone understand what is happening ? Any ideas on how to get past this ?
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...