Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Config help with egressing IOS static NAT

Hello all;

Simple question for you: Please look at the configuration below. I have a static NAT so ingress traffic from my Burbank VPN connects to 172.16.36.67, and this works well. However, when the inside host (192.168.1.14) responds bacl to the Burbank host, the inside local host isn?t translating into the static global IP of 172.16.36.67 but is translating into one of the available range of IP addresses from the pool.

Please tell me how to adjust my NAT statement to allow 192.168.1.14 to always map to 172.16.36.67 when communicating through route map BURBANK in either direction.

Regards

Jeff

access-list 101 permit ip 192.168.1.0 0.0.0.255 10.130.1.0 0.0.0.255

ip nat pool TOUCHPOOL 172.16.36.85 172.16.36.126 netmask 255.255.255.192

ip nat inside source static 192.168.1.14 172.16.36.67 route-map BURBANK

route-map BURBANK permit 49

match ip address 101

1 REPLY

Re: Config help with egressing IOS static NAT

Hi

Why you have used route-map BURBANK with the static NAT transalation command.

Chnage it to following:

ip nat inside source static 192.168.1.14 172.16.36.67

ip nat inside source route-map BURBANK pool TOUCHPOOL

This will work fine for you.

http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080093fca.shtml

http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080093fca.shtml

HTH, Please rate if it does.

-amit singh

112
Views
0
Helpful
1
Replies
CreatePlease login to create content