July 25, 2008 02:28pm pdt

Member Login

Top Experts

Yearly

1batry_boy 585,976
2lrmoore 215,525
3mkielar 102,700
4Voltz-dk 99,420
5MrHusy 90,695
6Cyclops3... 77,840
7PeteLong 71,000
8grblades 40,275
9JFrederic... 37,100
10nodisco 35,300
11raptorjb007 33,200
12rsivanandan 32,380
13from_exp 32,120
14mabutterfi... 27,200
152PiFL 25,575

null

	[x] Attachment Details

Cisco ASA 5510 Lan2Lan IPSec tunnel

Zones: Cisco PIX Firewall, Virtual Private Networking (VPN), IPSec Security Protocol

Hi all,

We would like to build an IPSec tunnel to a customer of ours. We have several tunnels and they are working fine, but this one just won't come up.
This is the scenario, we can use 2 ip adresses to connect to the customer, and we use natting to translate some IP ranges from the inside to those 2 ip adresses. When I start a ping from the inside (192.168.40.30 to be exact) to the cust.ip.addres.17 nothing happens.
I've tried debug crypto ipsec/isakmp but they don't show me any info on this tunnel. I don't see anything in the logs about this tunnel either. It seems that he doesn't use the tunnel to try to get to the customer ip.

What am I doing wrong?

Thanks!

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:

           
           
             Cisco Adaptive Security Appliance Software Version 7.2(3)
Device Manager Version 5.2(3)
 
access-list crypto_customer remark VPN Tunnel to customer
access-list crypto_customer extended permit ip our.ip.addr.104 255.255.255.254 cust.ip.addr.16 255.255.255.248
access-list nat_customer remark NAT for VPN tunnel to customer
access-list nat_customer extended permit ip 192.168.45.0 255.255.255.0 cust.ip.addr.16 255.255.255.248
access-list nat_customer extended permit ip host 192.168.40.30 cust.ip.addr.16 255.255.255.248
 
global (outside) 3 our.ip.addr.104
 
nat (inside) 3 access-list nat_customer
 
static (inside,outside) our.ip.addr.104 192.168.40.2 netmask 255.255.255.255 dns
static (inside,outside) our.ip.addr.105 192.168.40.67 netmask 255.255.255.255 dns
 
crypto ipsec transform-set ESP_AES_SHA esp-aes-256 esp-sha-hmac
 
crypto map outside_map 140 match address crypto_customer
crypto map outside_map 140 set pfs
crypto map outside_map 140 set peer PEERIP
crypto map outside_map 140 set transform-set ESP_AES_SHA
crypto map outside_map 140 set security-association lifetime seconds 3600
 
crypto map outside_map interface outside
crypto isakmp identity address
crypto isakmp enable outside
crypto isakmp policy 5
 authentication pre-share
 encryption aes-256
 hash sha
 group 2
 lifetime 86400
 
 
tunnel-group PEERIP type ipsec-l2l
tunnel-group PEERIP ipsec-attributes
 pre-shared-key *

           
         

Start your free trial to view this solution

[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!

6.2

Question Stats

Zone: Security

Question Asked By: o-tvw-ee

Solution Provided By: MrHusy

Participating Experts: 2

Solution Grade: B

Translate:

Loading Advertisement...

Open Discussion

null

Comment by MrHusy

"Hmm Rebooting the cisco's fixed the problem"
clear xlate should have done the same effect, was an interesting issue. But glad that it is sorted out
Thanks for points :)

null

Comment by o-tvw-ee

I cleared the xlate several times... This is probably a 'feature' of the ASA devices :)

null

Comment by ForestDenizen

Altered last code snippet to convert all IP addresses to 0.0.0.0 at 0-tvw-ee's request.

ForestDenizen
Community Support Moderator

20080723-EE-VQP-34 / EE_QW_2_20070628