I have a Nat design question. I would like enhance the communicaton that i have with a partner company.
The issue is that we use common ip addressing for several networks.
You can see in the attached diagram .
I have currently an ASA 8.2.5 which i recently upgraded to 9.1.5 in order to be able to configure twice nat. My issue is that some of my inside users must be able to communicate with networks 172.16.10.0 /24 & 172.16.11.0 /24 the networks are already utilized in my network as well.
Hence I created static nats (outside,inside) for the specific servers that must be accessed in the partner's network, the problem is that my partner needs the same source address from all of my inside users that connect to specific servers. For example anyone that wants to connect to the web-server 172.16.10.100 should come with source address 172.16.253.100, anyone that wants to connect to the FTP-server 172.16.10.200 should come with source address 172.16.253.200 and so on.
I was thinking that i could achieve this with twice nat (translating both source and destination, but after some experimenting i realized that this cannot be achieved with a single twice nat statement.
Between my routers there is a point to point mpls line which is secured by an ipsec vpn tunnel.
Can you please give me some suggestions on how can i overcome this issue.
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...