  rsreese
join:2004-02-17 Saint Augustine, FL
| [Config] site to site VPN issues using Cisco ASA 5500 to Router
Hey everyone I've been having a bit of a snag when trying to connect to point via VPN. One end is a ASA5505 and the other is a 3725 router. The network on the router side I'm trying to access is 172.16.2.x and on the ASA side 172.31.12.x.
I am able to initiate the connection from the ASA side but not from the router side. I am unable to transfer any data between to two hosts:
There no pong to my ping requests though. Also I've tried other services that fail. Here are my configurations. If anyone see's anything wrong feel free to let me know :-).
router
ASA
|
|
 kubaff
join:2007-06-14 kenya
| Re: [Config] site to site VPN issues using Cisco ASA 5500 to Rou
you need to EXCLUDE the INTERESTING traffic from being NAT'd on the router. Use an extended AccessList and make sure it's the FIRST ACL to be processed
ip nat inside source list 1 interface FastEthernet0/0 overload
# access-list 1 permit 172.16.2.0 0.0.0.255 # access-list 1 permit 172.16.3.0 0.0.0.255
Change ACL to
access-list xx deny 172.16.2.0 0.0.0.255 172.16.10.0 0.0.0.255 access-list xx deny 172.16.3.0 0.0.0.255 172.31.12.0 0.0.0.255 access-list xx permit 172.16.2.0 0.0.0.255 any access-list xx permit 172.16.3.0 0.0.0.255 any
ip nat inside source list x interface FastEthernet0/0 overload |
|
  rsreese
join:2004-02-17 Saint Augustine, FL
| reply to rsreese kubaff,
I changed the ACL for NAT as you mentioned to the following extended ACL's but it still didn't work:
Any other ideas? |
|
 aryoba Premium,MVM join:2002-08-22
| There is this forum FAQ link providing IPSec tunnel sample configuration between PIX (or ASA) and router.
»Cisco Forum FAQ »Various Site-to-Site IPSec VPN: Cisco, Juniper, Checkpoint, Sonicwall, Zywall |
|
  rsreese
join:2004-02-17 Saint Augustine, FL
1 edit | reply to rsreese I've been able to connect to the ASA to other ASA and PIX devices but not to the router. I imagine is something like a ACL issue or something I'm missing. Thanks for the links though.
I'm assuming since the ASA side can initiate the connection that there is a problem with the router side of things. |
|
 kubaff
join:2007-06-14 kenya
| reply to rsreese It's all in the NATing. I had a similar situation between a PIX and 2811
You need to make sure that the INTERESTING TRAFFIC in EXCLUDED from the Global NAT statement. In addition the "reverse" ACL (10) attached to the Crypto map.
access-list 10 permit 172.16.2.0 0.0.0.255 172.16.10.0 0.0.0.255 access-list 10 permit 172.16.3.0 0.0.0.255 172.31.12.0 0.0.0.255
crypto map CLIENTMAP 1 ipsec-isakmp set peer 1.1.1.1 set transform-set ESP-3DES-SHA match address 10
access-list 11 deny 172.16.2.0 0.0.0.255 172.16.10.0 0.0.0.255 access-list 11 deny 172.16.3.0 0.0.0.255 172.31.12.0 0.0.0.255 access-list 11 permit 172.16.2.0 0.0.0.255 any access-list 11 permit 172.16.3.0 0.0.0.255 any
ip nat inside source list 11 interface FastEthernet0/0 overload |
|
  rsreese
join:2004-02-17 Saint Augustine, FL
1 edit | kubaff,
I did something similar but used extended ACL's since standard didn't allow for the source IP to be listed:
access-list 150 deny ip 172.16.2.0 0.0.0.255 172.31.12.0 0.0.0.255 access-list 150 permit ip 172.16.2.0 0.0.0.255 any access-list 150 permit ip 172.16.3.0 0.0.0.255 any
I actually got the whole thing to work at one point last night by setting 'set pfs group1' to 'crypto map CLIENTMAP 1 ipsec-isakmp' but then I changed something when cleaning up and broke it. Slightly frustrating...
Here's the most recent config for the router:
|
|
 kubaff
join:2007-06-14 kenya | reply to rsreese Ran the CLEAR CRYPTO IPSEC SA
Could you display
- sh crypto isakmp sa - sh crypto isakmp ipsec
You could be having issues with IPSEC;
- debug crypto ipsec |
|
 kubaff
join:2007-06-14 kenya | reply to rsreese
sorry...
sh crypto ipsec sa |
|
  rsreese
join:2004-02-17 Saint Augustine, FL | reply to rsreese It was a issue with my connection renewing the lease on the IP. |
|
 thejipster
join:2008-05-20
| reply to rsreese FYI, I know you have solved this issue. This is mainly for other who run into this issue in the future. IPSEC router has pfs disabled by default.
Problem is that Cisco IOS IPSEC router will be able to accept PFS from the peer even if PFS is disabled.
But if ASA has PFS enabled, IPSEC router will fail the IPSEC negotiation since ASA will reject the IPSEC negotiation.
That explains the one-directional IPSEC setup issue. |
|
  rsreese
join:2004-02-17 Saint Augustine, FL | Thanks for the heads up. I realized that PFS was a issue between the two devices after many hours of trouble shooting  |
|