The 2 IP networks that you are referring, do you need complete 2-way communication between them or is it just going to be 1-way communication? if it is going to be 2-way communication, you will meed to statically translate both the networks to different subnets. That is assuming the follwing:
IP network: A/24
static (in,out) B A netmask 255.255.255.0
static (in,out) C A netmask 255.255.255.0
Now the IP network A in FWSM1 when trying to access the network behind FWSM2, they will actually need to specify the destination P in the subnet C (because of the static NAT) and also the source IP will get translated to an IP in the subnet B.
When the network behind FWSM2 tries to do the same, the destination will be specified in subnet B and the source IP will get translated to the subnet C.
We need to ensure all the corresponding ACLs and routing reflect these 2 IP subents, B and C.
Again, I am assuming that this is your network requirement and i hope i am correct Do send your detailed requirement if this is not the case and we can recommedations based on that.
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...