I've never had to can before over a VPN, I've been lucky I guess that both sides don't use the same IP range in the past. However, now I need NAT as the remote network is using a range we have. Users use servers on each side of the VPN and we use a ASA 5520 my side the other side is managed by another company and the VPN/Firewall is very basic (not sure of the make).
My network range is 192.168.0.0/16
Remote Network is 10.20.30.0/24 and various 192.168.x.x/24 addresses.
My network only need to reach the 10.20.30.x/24 range as that is where their servers are.
The remote network need to contact servers on my network on the 192.168.21.x/24 and 192.168.20.x/24 and 192.168.100.x/24 range. I was wondering if it is possible NAT our range(192.168.x.x/16) to 172.19.20./24 and then NAT our servers to these ranges for the remote office to connect to?
I just don't know where to satrt on this? I guess my phase to of the VPN will have to stay at SA 10.20.30.x/24 and theirs will have to be 172.19.20.x/24 so the tunnel comes up, then some sort of NAT from the 172.19,20.x range to our servers?
In the above example, PIX is doing bi-direction NAT. In your case, you must NAT your 192.168.x.x IP address. But if the source IP from the remote side is only from 10.20.30.x network, you don't need NAT it. If the packet from the remote end will be sourced from 192.168.x.x network as well, you will need bi-direction NAT as well.
I'll use another example that has risen today. Our network is on 192.168.x.x/16 and the remot VPN network is also on 192.168.x.x/16. The remote network only need to come inbound to us where the servers are, what options do we have?
I'm not sure if it is possible to have my nework NAT as 172.19.20.x/24 and keep the remote network as 192.168.x.x/16 then do some sort or PAT/NAT to our servers.
You have to NAT remote side network as well. Saying, remote side with IP address 192.168.x.x is accessing the server on your site. How your server to know if it is from the remote site or local network. Unless you have some special topology and routing setting which let your server know the difference.
You should have the access to the document if you have a cco account. Anyway, I attached its pdf file here.
If the server IP which you try to access is not overlap, you don't need static NAT, regular NAT/PAT should work. You need change the ACL which defines the interested traffic for IPSec tunnel as well. Its source IP should be NATed IP.
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...