VPN's and Nating

[mbroberson1]

We have a new cisco 3825 router that we use for site-to-site vpn's. Several of the vpn's need to access the same internal host. On one of the VPN's we are nating this particular internal host to the outside. On several other VPN's that need access to this same internal host we are not nating the host to the outside. How do you configure a VPN to nat an internal host ip to a remote VPN so it doesn't effect other VPN's that need access to the same internal host?

Thanks,

[JEREMY GRAY]

I'd have thought that ip nat inside source list would do this for you, identifying the source and destination in the ACL to qualify for that specific source IP to that specific destination be NAT, while the same source to a different destination would not match the ACL and would therefore not be NAT.

[mbroberson1]

We were wondering if we would need to do something with route-maps with this?

Thanks,

[a.ordonez]

That's correct. That's how we do it. I think it's the only way to do it. The access-list associated with the NAT route maps have to deny NAT'ing from internal node to far end internal node but allow NAT'ing when some public node tries to access your publicly accessible internal server.

[mbroberson1]

How many route-map statements do you typically need?

Thanks,