[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.0

Cisco ASA - create VPN tunnel using public IP address as the encryption domain

Asked by JammyPak in Cisco PIX Firewall, Networking Hardware Firewalls, Virtual Private Networking (VPN)

Tags: Cisco, ASA, VPN

I have a Cisco ASA that's being used for a bunch of different site-site tunnels.

There is a new request to create a tunnel to a cisco router at a remote site. The restriction is that they require that a public IP address be used for the encryption domain. In all of the previous tunnels, internal subnet addresses were used for the encryption domain to allow access back and forth through the tunnel. In this case, it's just required to have a single address as the encryption domain, and once the tunnel's up, the communication will really only occur one-way (from us to them) with them granting access to the public IP that is our encryption domain.

I'm not 100% sure what the easiest or correct way to set this up is. I have a spare ASA, so it doesn't all have to happen on the one ASA if it necessary to NAT one behind the other or something. I also have available public IPs on my external subnet, so I don't have to use the same public IP that is assigned to the ASA itself.

Bottom line is that we want a site-site tunnel on an ASA where both the tunnel endpoint and the encryption domain are public IP addresses, and we will access remote systems across that tunnel using primarily ssh.

Any and all assistance is appreciated...thanks.
[+][-]02/11/09 12:39 PM, ID: 23615900Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zones: Cisco PIX Firewall, Networking Hardware Firewalls, Virtual Private Networking (VPN)
Tags: Cisco, ASA, VPN
Sign Up Now!
Solution Provided By: Donboo
Participating Experts: 1
Solution Grade: A
 
[+][-]04/26/09 03:28 AM, ID: 24235487Administrative Comment

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 30-day free trial to view this Administrative Comment or ask the Experts your question.

 
 
Loading Advertisement...
20091111-EE-VQP-89 - Hierarchy / EE_QW_EXPERT_20070906