09-16-2009 06:22 AM
I have an ASA5520 running 8.0.4. I need to create a tunnel with a vendor using the same internal network as we are. They are unable NAT on their side. I would like both sides to be able to bring up the tunnel. They are using 10.2.x.x/16 as their internal network, as are we. The interesting traffic on my side would come from the nodes 10.0.194.1 and 10.0.194.5. How do I configure my side of the tunnel to get this to work?
Thanks,
Keith
09-17-2009 08:57 AM
Hello Keith,
I read through your question and it seems like your side will need to encrypt only 10.0.194.4 and 10.0.194.5 hosts to the remote peer 10.2.x.x/16
So, you should be able to bring up the tunnel and pass traffic without any issues.
If, they have the same network 10.0.194.x on their end as well, then you can do something called as policy NAT.
Please look at the link given below:
OR
In the above example, the 192.168.1.0 network on PIX-A side is getting policy NAT to 172.18.1.0 when the traffic is meant to go for 10.1.0.0/24 network.
**********
access-list policy-nat extended permit ip 192.168.1.0 255.255.255.0 10.1.0.0 255.255.255.0
static (inside,outside) 172.18.1.0 access-list policy-nat
********************
Hope this helps.
Thanks
Gilbert
09-17-2009 09:03 AM
We use the 10.2.x.x network internally already. So I can't route traffic destined for 10.2.x.x to a different location.
Thanks,
Keith
09-21-2009 06:31 AM
Keith
In that case, you can convert the remote network 10.2.x.x to something else on the ASA by using the static command.
Please read through the example given below.
OR
http://www.cisco.com/en/US/tech/tk583/tk372/technologies_configuration_example09186a00800949f1.shtml
Let me know if this helps.
Gilbert
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