Destination Pool NAT...???

[kasqureshii]

Hi everyone!

I've a scenario in which two pools 172.16.1.128/28 & 172.16.1.192/28 need to communicate with 10.240.224.0/24 over an IPsec tunnel. But the problem is that 10.240.224.0/24 is not unique on this side of the network. I need to apply NAT for destination subnet (10.240.224.0/24).

Is it possible that traffic is sourced from 172.16.1.128/28 & 172.16.1.192/28, destined to 172.28.33.0/24 actually reaches 10.240.224.0/24. How can I apply NAT in this scenario?

[Vasilii Mikhailovskii]

Hello.

Basically on remote side you need to make static 10.240.224.0/24 (inside local) -> 172.28.33.0/24 (inside global).

for IOS it should be something like:

ip nat inside source static network 10.240.224.0 172.28.33.0 /24

If you configure such a static on a remote site only, then local 10.240.224.0 could have an issue communicating with any remote subnet (depending on other NAT configuration). To fix this you need a simular static NAT (to a different /24 pool) on local site.

PS: please let us know what platform are you using, what are sample interface names and what kind of NAT do you implement (VTI, crypto map, etc.).