Policy Nat Cisco router

Need some help, setting up site-to-site VPN, ASA on one side and a Cisco 891 on my side.

The other side of the VPN requires that I NAT our inside address range to a single public IP that will be allowed on the VPN as our encryption domain.

The remote IP address that I need to communicate with over the tunnel is xxx.xxx.xxx.151. The local private address range is xxx.xxx.251.0/24 and the public IP that I am trying to NAT these inside addresses to is xxx.xxx.xxx.117.

Here is the basic setup:

ip nat pool test xxx.xxx.xxx.117 xxx.xxx.xxx.117 netmask

ip nat inside source route-map test pool test overload

route-map test permit 10
 match ip address 146

access-list 146 permit ip xxx.xxx.251.0 host xxx.xxx.xxx.151

crypto map VPN 1 ipsec-isakmp
 description Tunnel to test
 set peer xxx.xxx.xxx.150
 set transform-set aes-sha
 match address 145

access-list 145 permit ip host xxx.xxx.xxx.117 host xxx.xxx.xxx.151

access-list for the regular NAT overload for the internet with the deny statements for traffic for across the VPN:

access-list 100 deny   ip xxx.xxx.251.0 host xxx.xxx.xxx.151
access-list 100 deny   ip xxx.xxx.xxx.0 host xxx,xxx,xxx.151
access-list 100 deny   ip  xxx.xxx.251.0  xxx.xxx.xxx.0
access-list 100 deny   ip  xxx.xxx.251.0  xxx.xxx.xxx.0
access-list 100 deny   ip  xxx.xxx.251.0  xxx.xxx.xxx.0
access-list 100 deny   ip  xxx.xxx.251.0  xxx.xxx.xxx.0
access-list 100 deny   ip  xxx.xxx.251.0  xxx.xxx.xxx.0
access-list 100 permit ip xxx.xxx.251.0 any

When I try a ping to the remote host on the VPN (xxx.xxx.xxx.151) the local address that I ping from on the xxx.xxx.251.0 network is supposed to NAT to the xxx.xxx.xxx.117 address which is what is allowed across the VPN.

How ever when I look at the NAT translations, I don't see any translation between the inside local address of the device I ping from and the 117 public address.

Any help or suggestions would be helpful.
Who is Participating?
asavenerConnect With a Mentor Commented:
Try clearing the nat translations.  Also, sometimes removing and re-adding the nat commands at the interface level can fix weird little quirks like this.

Both those steps can be done with minimal impact.
The biggest cause of problems like this that I've encountered is typos.  Double check every line to make sure the IP addresses are correct.

Next, do a show access-list 150 and see if you're getting hits on the access list.
keagle79Author Commented:
That's just it, when i try to ping the address on the remote side of the tunnel and look at the access list for the NAT pool no hits.

The router never tries to NAT the inside address to the .117 address in the NAT pool.  Therefore the router never even tries to bring up the VPN tunnel.  I have set this up on other 800 series routers, but for some reason this 891 router doesn't seem to understand what to do.
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

Do you have ip nat inside and ip nat outside applied to the correct interfaces?
Also, try running "clear ip nat translations *".
keagle79Author Commented:
Regular NAT is working fine for internet traffic, the problem is just when I try to policy NAT the specific VPN traffic to the .117 public address.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.