ASA 5510 VPN site-to-site

[fillthy]

Hi, I was successful in getting a site to site vpn established..Well I think I have. Is there anything else I have to do to allow me to ping the private IP's on the remote site?

Local lan is 192.168.30.0 remote lan is 192.168.79.0

ASA Version 8.0(3)
!
hostname ciscoasa
enable password 8Ry2YjIyt7RRXU24 encrypted
names
!
interface Ethernet0/0
nameif inside
security-level 100
ip address 192.168.30.3 255.255.255.0
!
interface Ethernet0/1
nameif outside
security-level 0
pppoe client vpdn group cppgroup
ip address 76.65.x.x 255.255.255.255 pppoe
!
interface Ethernet0/2
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet0/3
shutdown
no nameif
no security-level
no ip address
!
interface Management0/0
nameif management
security-level 100
ip address 192.168.1.1 255.255.255.0
management-only
!
passwd 2KFQnbNIdI.2KYOU encrypted
ftp mode passive
same-security-traffic permit intra-interface
access-list outside_1_cryptomap extended permit ip 192.168.30.0 255.255.255.0 any
access-list inside_nat0_outbound extended permit ip 192.168.30.0 255.255.255.0 host 66.35.179.154
access-list 101 extended permit icmp any any echo
access-list 101 extended permit icmp any any echo-reply
access-list 101 extended permit tcp any interface outside eq 3390
access-list 101 extended permit tcp any interface outside eq 3391
access-list 101 extended permit tcp any interface outside eq www
access-list 101 extended permit tcp any interface outside eq pop3
access-list 101 extended permit tcp any interface outside eq smtp
access-list 101 extended permit tcp any interface outside eq telnet
access-list 101 extended permit tcp any interface outside eq https
access-list 101 extended permit tcp any interface outside eq 10904
access-list 101 extended permit tcp any interface outside eq ftp
access-list 101 extended permit tcp any interface outside eq 3389
access-list inside_nat0_outbound_1 extended permit ip 192.168.30.0 255.255.255.0 192.168.79.0 255.255.255.0
access-list outside_1_cryptomap_1 extended permit ip 192.168.30.0 255.255.255.0 192.168.79.0 255.255.255.0
pager lines 24
logging asdm informational
mtu inside 1500
mtu outside 1500
mtu management 1500
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-603.bin
no asdm history enable
arp timeout 14400
global (outside) 101 interface
nat (inside) 0 access-list inside_nat0_outbound_1
nat (inside) 101 0.0.0.0 0.0.0.0
static (inside,outside) tcp interface 3390 192.168.30.x 3390 netmask 255.255.255.255
static (inside,outside) tcp interface 3391 192.168.30.x 3391 netmask 255.255.255.255
static (inside,outside) tcp interface 3389 192.168.30.x 3389 netmask 255.255.255.255
static (inside,outside) tcp interface

http://www 192.168.30.x

http://www netmask

255.255.255.255
static (inside,outside) tcp interface pop3 192.168.30.x pop3 netmask 255.255.255.255
static (inside,outside) tcp interface smtp 192.168.30.x smtp netmask 255.255.255.255
static (inside,outside) tcp interface telnet 192.168.30.x telnet netmask 255.255.255.255
static (inside,outside) tcp interface https 192.168.30.x https netmask 255.255.255.255
static (inside,outside) tcp interface 10904 192.168.30.x 10904 netmask 255.255.255.255
static (inside,outside) tcp interface ftp 192.168.30.x ftp netmask 255.255.255.255
access-group 101 in interface outside
route outside 0.0.0.0 0.0.0.0 76.65.x.x 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout uauth 0:05:00 absolute
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 192.168.1.0 255.255.255.0 management
http 192.168.30.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set transform-set ESP-3DES-SH
A
crypto map outside_map 1 match address outside_1_cryptomap_1
crypto map outside_map 1 set pfs
crypto map outside_map 1 set peer 66.35.x.x
crypto map outside_map 1 set transform-set ESP-3DES-SHA
crypto map outside_map interface outside
crypto isakmp enable outside
crypto isakmp policy 10
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
no crypto isakmp nat-traversal
telnet timeout 5
ssh timeout 5
console timeout 0
vpdn group cppgroup request dialout pppoe
vpdn group cppgroup localname canada111@bellnet.ca
vpdn group cppgroup ppp authentication pap
vpdn username cppgroup password ********* store-local
vpdn username canadaxxxx@bellnet.ca password *********
dhcpd address 192.168.1.2-192.168.1.254 management
dhcpd enable management
!
threat-detection basic-threat
threat-detection statistics access-list
tunnel-group 66.35.x.x type ipsec-l2l
tunnel-group 66.35.x.x ipsec-attributes
pre-shared-key *
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
!
service-policy global_policy global
prompt hostname context
Cryptochecksum:73a919a02343fa36b3fd52ec1bff3815
: end

 

[nnnnnnnnnn]

Here is how I typically check to see if a tunnel is working. ping the other side inside interface sourcing from the asa interface. you will need to enable icmp and managment-acces to the inside interface. check ipsea and isakmp associations. hope that helps

cheers

icmp permit any inside
management-access inside

ping inside 192.168.100.1

show crypto ipsec sa
show crypto isakmp sa

 

[fillthy]

getting these errors in the log

5|Feb 15 2008|09:48:21|713068|||Group = 66.35.x.x, IP = 66.35.x.x, Received non-routine Notify message: No proposal chosen (14)
3|Feb 15 2008|09:48:21|713119|||Group = 66.35.x.x, IP = 66.35.x.x, PHASE 1 COMPLETED
4|Feb 15 2008|09:48:21|713903|||Group = 66.35.x.x, IP = 66.35.x.x, Freeing previously allocated memory for authorization-dn-attributes
5|Feb 15 2008|09:48:21|713073|||Group = 66.35.x.x, IP = 66.35.x.x, Responder forcing change of IKE rekeying duration from 86400 to 28800 seconds
5|Feb 15 2008|09:48:20|713041|||IP = 66.35.x.x, IKE Initiator: New Phase 1, Intf inside, IKE Peer 66.35.x.x local Proxy Address 192.168.30.0, remote Proxy Address 192.168.79.0, Crypto map (outside_map)
4|Feb 15 2008|09:48:17|113019|||Group = 66.35.x.x, Username = 66.35.x.x, IP = 66.35.x.x, Session disconnected. Session Type: IKE, Duration: 0h:00m:10s, Bytes xmt: 0, Bytes rcv: 0, Reason: Phase 2 Mismatch
3|Feb 15 2008|09:48:17|713902|||Group = 66.35.x.x, IP = 66.35.x.x, Removing peer from correlator table failed, no match!
1|Feb 15 2008|09:48:17|713900|||Group = 66.35.x.x, IP = 66.35.x.x, construct_ipsec_delete(): No SPI to identify Phase 2 SA!
3|Feb 15 2008|09:48:17|713902|||Group = 66.35.x.x, IP = 66.35.x.x, QM FSM error (P2 struct &0xd56249b8, mess id 0xb1c3c58c)!
5|Feb 15 2008|09:48:17|713904|||Group = 66.35.x.x, IP = 66.35.x.x, All IPSec SA proposals found unacceptable!
5|Feb 15 2008|09:48:14|713068|||Group = 66.35.x.x, IP = 66.35.x.x, Received non-routine Notify message: No proposal chosen (14)
5|Feb 15 2008|09:48:06|713068|||Group = 66.35.x.x, IP = 66.35.x.x, Received non-routine Notify message: No proposal chosen (14)
3|Feb 15 2008|09:48:06|713119|||Group = 66.35.x.x, IP = 66.35.x.x, PHASE 1 COMPLETED
4|Feb 15 2008|09:48:06|713903|||Group = 66.35.x.x, IP = 66.35.x.x, Freeing previously allocated memory for authorization-dn-attributes
5|Feb 15 2008|09:48:06|713073|||Group = 66.35.x.x, IP = 66.35.x.x, Responder forcing change of IKE rekeying duration from 86400 to 28800 seconds
5|Feb 15 2008|09:48:06|713041|||IP = 66.35.x.x, IKE Initiator: New Phase 1, Intf inside, IKE Peer 66.35.x.x local Proxy Address 192.168.30.0, remote Proxy Address 192.168.79.0, Crypto map (outside_map)
4|Feb 15 2008|09:48:05|419002|192.168.30.181|192.168.0.180|Duplicate TCP SYN from inside:192.168.30.181/1044 to outside:192.168.0.180/50797 with different initial sequence number
4|Feb 15 2008|09:48:03|419002|192.168.30.181|192.168.0.180|Duplicate TCP SYN from inside:192.168.30.181/1044 to outside:192.168.0.180/50797 with different initial sequence number
5|Feb 15 2008|09:47:48|713904|||IP = 66.35.x.x, Received encrypted packet with no matching SA, dropping
4|Feb 15 2008|09:47:38|106023|64.230.160.109|76.65.x.x|Deny icmp src outside:64.230.160.109 dst inside:76.65.x.x (type 11, code 0) by access-group "101" [0x0, 0x0]
5|Feb 15 2008|09:47:31|713904|||IP = 66.35.x.x, Received encrypted packet with no matching SA, dropping
4|Feb 15 2008|09:47:28|419002|192.168.30.181|192.168.0.180|Duplicate TCP SYN from inside:192.168.30.181/1044 to outside:192.168.0.180/50797 with different initial sequence number
5|Feb 15 2008|09:47:22|713904|||IP = 66.35.x.x, Received encrypted packet with no matching SA, dropping
4|Feb 15 2008|09:47:22|419002|192.168.30.181|192.168.0.180|Duplicate TCP SYN from inside:192.168.30.181/1044 to outside:192.168.0.180/50797 with different initial sequence number

 

[nnnnnnnnnn]

I think this is the important error

4|Feb 15 2008|09:48:17|113019|||Group = 66.35.x.x, Username = 66.35.x.x, IP = 66.35.x.x, Session disconnected. Session Type: IKE, Duration: 0h:00m:10s, Bytes xmt: 0, Bytes rcv: 0, Reason: Phase 2 Mismatch


In order for two peers to successfully negotiate an IPsec SA, they must agree on three things specific to Phase 2 negotiation:

The IP addresses used for IPsec tunnel termination

The symmetric IPsec transforms to use on crypto-protected traffic after an IPsec SA has been negotiated

The scope of protected traffic in the crypto switching path


I would check the acl and the crypto transform set used on both sides of the tunel and make sure they match

 

[fillthy]

Hi, thanks for that, it will give me something to check. The other end has limited settings..Its a Sonicwall. Does this help any?
Cheers

 

[Supergrrover]

Also check what the PFS setting for the Sonicwall is. I believe that it is set to off by default. (Your config shows yours is set to on.)

Here is the Cisco doc to run through and check. It has screen shots of the sonicwall.

http://www.cisco.com/en/US/products...s_configuration_example09186a008052c9d4.shtml

Brent
Systems Engineer / Consultant
CCNP, CCSP

 

[nnnnnnnnnn]

actually that complicates things. I was kind of hoping the peer was a pix or router. Sonicwalls are not something I am no so savvy with. I did find an artical on cisco.com with an example on how this is done. I did notice Cisco used aes-256 with sha but you are using 3des with sha, but I would assume 3des is also an option. I would also look though the sonicwall config portion and make sure it agrees with Cisco. hope that helps

cheers

http://www.cisco.com/en/US/products...s_configuration_example09186a008052c9d4.shtml