Yes, it is ok to create static mappings for multiple blocks of ips/netwroks on the pix, and no the static entries all don't have to be within the range of the pix's external interface IP? But, you need to make sure that you create route for these ips/networks poiting to the outside interface of the pix as next-hop on the router connected to the outside interface of the pix.
We have a PIX static mappings for two blocks of IPs. The outside interface of the firewall is connected to a Cisco 2621 router. The router's Ethernet interface has the primary IP address in the same subnet as the PIX outside interface. We have also assigned a secondary IP address to the Interface in the other IP block (which has the static mapping on the PIX).
This set up was working well with PIX 6.2. We were able to access the hosts inside the PIX which have static mapping to both the IP blocks.
When we upgaded the PIX OS to 6.3.1, the static mapping for the second IP block not working. Only the static mapping for the IP block which is the same as the ouside Interface is working.
We are not having any static routes on the router pointing to the PIX outside interface for the second IP block. We only assigned a secondary IP address from this block for the router's Ethernet interface.
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...