Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

ASA EasyVPN Hairpinning

Posted on 2008-10-07
1
Medium Priority
?
409 Views
Last Modified: 2013-11-16
Hi!

I like to connect a number of asa5505 to a central asa5510 using easyvpn. There is no problem with vpn-tunnels since the local offices are connected and traffic is passing through the tunnels (internet browsing is ok).

My problem is that since the tunnels are terminated at the same interface, i can't figure out if there shall be same nat rules to permit traffic between the 2 sites.. and if it shall, how will they look?

For exempel:

firewall A has 192.168.15.0/24 as inside network and is attached to firewall C at interface 172.28.3.254
firewall B has 192.168.16.0/24 as inside network and is attached to firewall C at interface 172.28.3.254

I like to be able to ping 192.168.15.100 ( or any other adress at that net) from 192.168.16.0/24 and reverse
 
I have used the: "same-security-traffic permit intra-interface" command and local offices are in "network extension mode" but still no success..

Any ideas?
0
Comment
Question by:Swedish
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 8

Accepted Solution

by:
Jay_Gridley earned 2000 total points
ID: 22667157
You should exempt the 'internal' traffic through the tunnel from NAT. You can do that using an access-list.

First create the access-list:
access-list inside_nat0_outbound extended permit ip 192.168.15.0 255.255.255.0 172.28.3.254 255.255.255.0

Then tell the ASA to use this access-list for NAT0 (i.e. don't NAT):
nat (inside) 0 access-list inside_nat0_outbound

You should create a similar access-list (but the other way around) on both sides of your tunnel. You can just add additional entries to the access-list for additional sites.

Good luck.

JG.
0

Featured Post

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The DROP (Spamhaus Don't Route Or Peer List) is a small list of IP address ranges that have been stolen or hijacked from their rightful owners. The DROP list is not a DNS based list.  It is designed to be downloaded as a file, with primary intention…
This article offers some helpful and general tips for safe browsing and online shopping. It offers simple and manageable procedures that help to ensure the safety of one's personal information and the security of any devices.
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…
Suggested Courses

604 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question