04-03-2018 09:36 AM - edited 03-08-2019 02:30 PM
I have been researching this for a few days and still cannot get a simple NAT to work. We need to access a server but have overlapping IP's in our networks. Do I need "one-to-one" NAT statements? Does this require an ACL and or Route-map?
Goal: NAT 4 IP's.
10.1.29.1 NAT 10.52.100.1
10.1.29.2 NAT 10.52.100.2
10.1.29.3 NAT 10.52.100.3
10.1.29.4 NAT 10.52.100.4
Destination: 172.19.0.39
Router Interfaces:
Gig0/1.52 - Inside facing users on 10.1.29.0/24: ip nat inside
Serial1/0 - Outside towards server: ip nat outside
Switch --> Router (NAT) --> MPLS Network --> Server
10.1.29.1 --> 10.52.100.1 --> MPLS Network --> 172.19.0.39
Thank you!
Solved! Go to Solution.
04-03-2018 09:41 AM
If you always to NAT those internal IPs to the same external IP -
"ip nat inside source static 10.1.29.1 10.52.1.100"
etc. for each IP address assuming none of the 10.52.x.x IPs are assigned to one of the interfaces on the router.
Or you could just NAT all the 10.1.29.x IPs to the same 10.52.1.x IP and save a few IPs if the connection is always initiated from the 10.1.29.x side which it sounds like it is.
Up to you.
Jon
04-03-2018 09:41 AM
If you always to NAT those internal IPs to the same external IP -
"ip nat inside source static 10.1.29.1 10.52.1.100"
etc. for each IP address assuming none of the 10.52.x.x IPs are assigned to one of the interfaces on the router.
Or you could just NAT all the 10.1.29.x IPs to the same 10.52.1.x IP and save a few IPs if the connection is always initiated from the 10.1.29.x side which it sounds like it is.
Up to you.
Jon
04-03-2018 11:48 AM
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: