Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 675
  • Last Modified:

Cisco ASA NAT question

Imagine two ASAs connecting via IPSec tunnel over the Internet.  
Inside IP of ASA-1 is 10.10.1.1 while inside IP of ASA-2 is 10.10.2.1.
There is a router inside of ASA-2 at 10.10.2.5.  And on the far side
of that router (let's call it R2) - is network 192.168.77.0/24.  
If I am on a host inside ASA-1 say 10.10.1.100 - I can ping R2
no problem (10.10.2.5).  The encryption domain for ASA-1 says
encrypt any traffic destined for 10.10.2.0 or 192.168.77.0/24.
The encryption domain ASA-2 says encrypt any traffic to 10.10.1.0/24.

Now let's say that R2 only wants to receive traffic from IP addresses
in the 10.10.2.0/24 subnet.  So I add at ASA-2:

static (Outside,inside) 10.10.2.100 10.10.1.100 netmask 255.255.255.255

I want to ping 192.168.77.100 from host 10.10.1.100.  
Would there be any special considerations for the reply traffic being able
to return to 10.10.1.100 over the tunnel?  That is the ICMP Echo Req
hits R2 with source 10.10.2.100 and dest 192.168.77.100.  The
reply comes back to 10.10.2.100 on the ASA.  The ASA would then need to
"un-nat" that to 10.10.1.100 and bring the reply safely home to
10.10.1.100.  Should that work?  I have not had to have this post-tunnel
nat before and would appreciate insight from anyone who might have
done this in the past.  

Thanks!
2013-05-15-16.23.55.jpg
0
amigan_99
Asked:
amigan_99
  • 2
  • 2
1 Solution
 
Cyclops3590Commented:
i'm not sure why you're adding the static command to ASA-2 to be honest.  It sounds like all of that traffic should be part of ACLs that get applied to nat 0.

ASA-1 - nat 0 - 10.10.2.0/24 to 10.10.1.0/24 or 192.168.77.0/24
ASA-2 - nat 0 - 10.10.1.0/24 or 192.168.77.0/24 to 10.10.2.0/24

then make sure each uses those for the crypto map as well which it sounds like you have.  As long as routing working on the R2 to forward packets to the ASA-2 (a default route will work) then you should be fine and be able to ping one another.

or am I missing something?
0
 
asavenerCommented:
The encryption domain for ASA-1 says
encrypt any traffic destined for 10.10.2.0 or 192.168.77.0/24.
The encryption domain ASA-2 says encrypt any traffic to 10.10.1.0/24.
I always make the access lists for my IPSec tunnels exactly reciprocal; I've had trouble bringing up the VPN if this isn't the case.....
0
 
asavenerCommented:
Should that work?  I have not had to have this post-tunnel
nat before and would appreciate insight from anyone who might have
done this in the past.  
Yes, this will work.  There's an order of operations, and NAT occurs before crypto.  (for outbound traffic.  For inbound traffic it's decrypt then NAT.

You have to make sure not to use an IP address that conflicts with other devices on the 10.10.1.0/24 network, though.  Because of this, NAT'ing the entire subnet will not work.

You might have to adjust any access lists on ASA1.  I honestly can't remember if the VPN traffic gets evaluated, and if so, if it's the original or NAT'd address that's evaluated.
0
 
Cyclops3590Commented:
btw, you'd need to setup a route on the ASA to forward traffic for 192.168.77.0/24 to R2 as well.
0
 
amigan_99Author Commented:
Yes it did.  Thank you for the reminder on the order of operations.
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now