03-29-2017 09:43 AM - edited 03-08-2019 09:58 AM
Solved! Go to Solution.
03-29-2017 12:59 PM
Okay so you need to use policy NAT ie. you only want to translate 10.61.13.0/24 to 10.104.204.19 when using the VPN. So firstly remove that NAT statement -
"no nat (inside) 2 10.9.160.0 255.255.254.0 0 0"
then define an acl for the VPN traffic -
"access-list <name> permit ip 10.61.13.0 255.255.255.0 10.9.160.0 255.255.254.0"
"access-list <name> permit ip 10.61.13.0 255.255.255.0 10.17.160.0 255.255.254.0"
then tie it the global statement so -
"nat (inside) 2 access-list <name>"
Jon
03-29-2017 09:49 AM
Your configuration is a little confusing ie. you have -
nat (inside) 2 10.9.160.0 255.255.254.0 0 0 <-- this is one of the remote networks
global (inside) 2 10.104.204.19
but then you say you are trying to NAT 10.61.13.0/24 to 10.104.204.19.
Is there a typo in the above ?
Jon
03-29-2017 10:53 AM
I'm a little confusing, but Yes,
I'm trying to translate 10.61.13.0/24 to 10.104.204.19 before entering the VPN tunnel over Internet
Remote networks route only 10.104.204.19 and they don't know 10.61.13.0/24
Thank you very much.
I think the prb is in these configs (but no idea where)
03-29-2017 12:59 PM
Okay so you need to use policy NAT ie. you only want to translate 10.61.13.0/24 to 10.104.204.19 when using the VPN. So firstly remove that NAT statement -
"no nat (inside) 2 10.9.160.0 255.255.254.0 0 0"
then define an acl for the VPN traffic -
"access-list <name> permit ip 10.61.13.0 255.255.255.0 10.9.160.0 255.255.254.0"
"access-list <name> permit ip 10.61.13.0 255.255.255.0 10.17.160.0 255.255.254.0"
then tie it the global statement so -
"nat (inside) 2 access-list <name>"
Jon
03-30-2017 02:19 PM
Really I'm still not able to close phase 2, but the prb now is on the other side,
Thank you very much Jon
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide