ASA 5505 9.1.3 Site to Site VPN Connection Profile Nat Exempt

Hi all,

On a Cisco ASA 5505 running 9.1.3.  Under one of my connection profiles for a site to site VPN there is an option for Exempt ASA side host/network from address translation (Inside interface).  That option is checked.

In the NAT rules there are several Section 1 and/or Manual NAT rules basically allowing the inside interface of the ASA to talk to different subnets on opposite side of the VPN in question.  If I do a sh NAT DETAIL Command I can see the rules as follows:

Manual NAT Policies (Section 1)
1 (inside) to (outside) source static inside inside   destination static OR_VOIP OR_VOIP
    translate_hits = 45, untranslate_hits = 54
    Source - Origin: 192.168.108.0/24, Translated: 192.168.108.0/24
    Destination - Origin: 172.16.0.0/22, Translated: 172.16.0.0/22
2 (inside) to (outside) source static inside inside   destination static OR_Dot4 OR_Dot4
    translate_hits = 18, untranslate_hits = 18
    Source - Origin: 192.168.108.0/24, Translated: 192.168.108.0/24
    Destination - Origin: 192.168.4.0/24, Translated: 192.168.4.0/24
3 (inside) to (outside) source static inside inside   destination static TT_LAN TT_LAN
    translate_hits = 87, untranslate_hits = 87
    Source - Origin: 192.168.108.0/24, Translated: 192.168.108.0/24
    Destination - Origin: 192.168.121.0/24, Translated: 192.168.121.0/24
4 (inside) to (outside) source static inside inside   destination static OR_Dot0 OR_Dot0
    translate_hits = 90, untranslate_hits = 91
    Source - Origin: 192.168.108.0/24, Translated: 192.168.108.0/24
    Destination - Origin: 192.168.0.0/24, Translated: 192.168.0.0/24

Being that the  "Exempt ASA side host/network from address translation" box is checked under the VPN connection profile do I still need these NAT rules?

Having a hard time finding out exactly what that check box does.   Thanks.
ckangas7Asked:
Who is Participating?
 
Michael OrtegaConnect With a Mentor Sales & Systems EngineerCommented:
You don't want proxy arp to be enabled across your NAT VPN, but your do want route-lookup. If you run "show nat" you should see at the end of your VPN NAT statements "no-proxy-arp route-lookup".

MO
0
 
Michael OrtegaSales & Systems EngineerCommented:
add no-proxy-arp route-lookup to the end of your site to site tunnel NAT statements on both sides.

MO
0
 
ckangas7Author Commented:
Thank you for the answer, but it really doesn't answer my question.  What does "Exempt ASA side host/network from address translation" box do?

Why do I need to add the no proxy-arp route-lookup to my Nat rules?
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
Michael OrtegaSales & Systems EngineerCommented:
It turns off NAT which is what you'd typically do in a traditional site to site VPN tunnel. Both sites would have that exemption set. You don't typically want the private networks on either side of the tunnel to translate to the global/public IP of the ASA.

turning off proxy-arp will allow the LAN sides of your tunnel to communicate with the LAN side interface of the opposing ASA.

To answer to your question, the NAT rules created are the result of turning on the exemption.

MO
0
 
ckangas7Author Commented:
So I think I am following you.  If I add the no proxy-arp to my NAT statements should the above translations shown with the 'Show NAT Detail' go away?  The way I read it now traffic is being translated, it is just not being translated to a public IP.  Checking NAT exemption with no proxy arp should allow traffic to flow freely across the VPN tunnel with routing being handled by the ASA or a router/switch on the other end.  Am I understanding correctly?
0
 
Michael OrtegaSales & Systems EngineerCommented:
Actually, the NAT detail you have above is showing that the traffic is not being translated. In the old ASA/PIX days we called this "no NAT". You're essentially telling the ASA to not translate the traffic. Source and destination traffic retain the untranslated version of their subnets. In a standard/traditional configuration this is the right way to do it. Assuming that everything else in your configuration regarding the Site to Site tunnels is correct there is no need to modify your NAT configuration. The "no-proxy-arp" option simply turns proxy arp off so that the LAN side interfaces of your ASA's can communicate to the opposing side of the tunnel.

MO
0
 
ckangas7Author Commented:
I get it.  One final question and I believe we are done : - ).  When I set up a site to site VPN tunnel via the wizard it automatically creates a NAT rule for me.  This NAT rule has the 'Disable Proxy ARP on egress interface' box checked as well as the 'Lookup route to locate egress interface' box checked.  This works fine and the sh nat detail shows the same results as above.  

However if I uncheck those two boxes and change the direction to both on the said NAT rule I get the following  warning.

Nat Warning
This configuration also works fine and the Show NAT detail is the same.

So the final question is which configuration is better and is the warning something I really need to worry about.
0
 
ckangas7Author Commented:
Very good.  Thank you much.  I get it now.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.