vpn tunnel between wrvs4400n and pix506e

Unanswered Question
May 27th, 2010
User Badges:

i can't get a vpn tunnel established between a wrvs4400n and a pix 506e. the pix has another tunnel configured and runs (with a linksys befvp41).


from the logs:


May 27 13:10:26  - [VPN Log]: Starting Pluto (Openswan Version  cvs2006Jan12_11:29:56 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR;  Vendor ID OE@ECqImzhFD)
May 27 13:10:26  - [VPN Log]: @(#) built on Aug 13  2009:02:39:00:
May 27 13:10:26  - [VPN Log]: Setting NAT-Traversal port-4500  floating to on
May 27 13:10:26  - [VPN Log]:    port floating activation  criteria nat_t=1/port_fload=1
May 27 13:10:26  - [VPN Log]:   including NAT-Traversal patch  (Version 0.6c)
May 27 13:10:26  - [VPN Log]: ike_alg_register_enc():  Activating OAKLEY_AES_CBC: Ok (ret=0)
May 27 13:10:26  - [VPN Log]: starting up 1 cryptographic  helpers
May 27 13:10:26  - [VPN Log]: started helper pid=3242 (fd:5)
May 27 13:10:26  - [VPN Log]: Using KLIPS IPsec interface  code on 2.4.27-star
May 27 13:10:26  - [VPN Log]: Changing to directory  '/etc/ipsec.d/cacerts'
May 27 13:10:26  - [VPN Log]: Changing to directory  '/etc/ipsec.d/aacerts'
May 27 13:10:26  - [VPN Log]: Changing to directory  '/etc/ipsec.d/ocspcerts'
May 27 13:10:26  - [VPN Log]: Changing to directory  '/etc/ipsec.d/crls'
May 27 13:10:26  - [VPN Log]:   Warning: empty directory
May 27 13:10:26  - [VPN Log]: added connection description  "lvl"
May 27 13:10:26  - [VPN Log]: listening for IKE messages
May 27 13:10:26  - [VPN Log]: adding interface ipsec0/eth1 123.456.2.214:500
May 27 13:10:26  - [VPN Log]: adding interface ipsec0/eth1 123.456.2.214:4500
May 27 13:10:26  - [VPN Log]: loading secrets from  "/etc/ipsec.secrets"
May 27 13:10:27  - [VPN Log]: "lvl": route-client output: 0
May 27 13:10:27  - [VPN Log]: "lvl" #1: initiating Main Mode
May 27 13:10:27  - [VPN Log]: "lvl" #1: transition from state  STATE_MAIN_I1 to state STATE_MAIN_I2
May 27 13:10:27  - [VPN Log]: "lvl" #1: STATE_MAIN_I2: sent  MI2, expecting MR2
May 27 13:10:27  - [VPN Log]: "lvl" #1: received Vendor ID  payload [XAUTH]
May 27 13:10:28  - [VPN Log]: "lvl" #1: received Vendor ID  payload [Dead Peer Detection]
May 27 13:10:28  - [VPN Log]: "lvl" #1: received Vendor ID  payload [Cisco-Unity]
May 27 13:10:28  - [VPN Log]: "lvl" #1: ignoring unknown  Vendor ID payload [152d138a3a936dded0c87c9e4652ade9]
May 27 13:10:28  - [VPN Log]: "lvl" #1: I did not send a  certificate because I do not have one.
May 27 13:10:28  - [VPN Log]: "lvl" #1: transition from state  STATE_MAIN_I2 to state STATE_MAIN_I3
May 27 13:10:28  - [VPN Log]: "lvl" #1: STATE_MAIN_I3: sent  MI3, expecting MR3
May 27 13:10:28  - [VPN Log]: "lvl" #1: Main mode peer ID is  ID_IPV4_ADDR: '654.321.80.66'
May 27 13:10:28  - [VPN Log]: "lvl" #1: transition from state  STATE_MAIN_I3 to state STATE_MAIN_I4
May 27 13:10:28  - [VPN Log]: "lvl" #1: STATE_MAIN_I4: ISAKMP  SA established {auth=OAKLEY_PRESHARED_KEY cipher=oakley_3des_cbc_192  prf=oakley_md5 group=modp1024}
May 27 13:10:28  - [VPN Log]: "lvl" #2: initiating Quick Mode  PSK+ENCRYPT+TUNNEL+DISABLEARRIVALCHECK+UP {using isakmp#1}
May 27 13:10:28  - [VPN Log]: "lvl" #1: ignoring  informational payload, type IPSEC_INITIAL_CONTACT
May 27 13:10:28  - [VPN Log]: "lvl" #1: received and ignored  informational message
May 27 13:10:28  - [VPN Log]: "lvl" #2: ignoring  informational payload, type IPSEC_RESPONDER_LIFETIME
May 27 13:10:28  - [VPN Log]: "lvl" #2: transition from state  STATE_QUICK_I1 to state STATE_QUICK_I2
May 27 13:10:28  - [VPN Log]: "lvl" #2: STATE_QUICK_I2: sent  QI2, IPsec SA established {ESP=>0xc5433c13 <0xfc84cdf8  xfrm=3DES_0-HMAC_MD5 NATD=none DPD=none}
May 27 13:10:30  - [VPN Log]: "lvl" #3: initiating Quick Mode  PSK+ENCRYPT+TUNNEL+DISABLEARRIVALCHECK+UP {using isakmp#1}
May 27 13:10:30  - [VPN Log]: "lvl" #3: ignoring  informational payload, type IPSEC_RESPONDER_LIFETIME
May 27 13:10:30  - [VPN Log]: "lvl" #3: transition from state  STATE_QUICK_I1 to state STATE_QUICK_I2
May 27 13:10:30  - [VPN Log]: "lvl" #3: STATE_QUICK_I2: sent  QI2, IPsec SA established {ESP=>0xb54e952d <0xfc84cdf9  xfrm=3DES_0-HMAC_MD5 NATD=none DPD=none}

the pix config is:

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";}


fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
name 172.16.1.0 site1
access-list inside_outbound_nat0_acl permit ip 192.168.1.0 255.255.255.0 site1 255.255.255.0
access-list inside_outbound_nat0_acl permit ip 10.10.10.0 255.255.255.0
site1 255.255.255.0
access-list inside_outbound_nat0_acl permit ip 10.10.11.0 255.255.255.0
site1 255.255.255.0
access-list inside_outbound_nat0_acl permit ip 192.168.1.0 255.255.255.0 10.10.100.0 255.255.255.0
access-list outside_cryptomap_20 permit ip 192.168.1.0 255.255.255.0
site1 255.255.255.0
access-list outside_cryptomap_20 permit ip 10.10.10.0 255.255.255.0
site1 255.255.255.0
access-list outside_cryptomap_20 permit ip 10.10.11.0 255.255.255.0
site1 255.255.255.0

access-list outside_cryptomap_30 permit  ip 192.168.1.0 255.255.255.0 10.10.100.0 255.255.255.0
mtu outside 1500
mtu inside 1500
ip address outside 654.321.80.66 255.255.255.240
ip address inside 192.168.1.1 255.255.255.0
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) 654.321.80.67 192.168.1.10 netmask 255.255.255.255 0 0
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 654.321.80.65 1
route inside 10.10.10.0 255.255.255.0 192.168.1.250 1
route inside 10.10.11.0 255.255.255.0 192.168.1.250 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto map outside_map 20 ipsec-isakmp
crypto map outside_map 20 match address outside_cryptomap_20
crypto map outside_map 20 set peer 456.789.223.90
crypto map outside_map 20 set transform-set ESP-DES-MD5
crypto map outside_map 30 ipsec-isakmp
crypto map outside_map 30 match address outside_cryptomap_30
crypto map outside_map 30 set peer 123.456.2.214
crypto map outside_map 30 set transform-set ESP-3DES-MD5
crypto map outside_map 30 set security-association lifetime seconds 14400 kilobytes 4608000
crypto map outside_map interface outside
isakmp enable outside
isakmp key ******** address 456.789.223.90 netmask 255.255.255.255 no-xauth no-config-mode
isakmp key ******** address 123.456.2.214 netmask 255.255.255.255 no-xauth no-config-mode
isakmp identity address
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
isakmp policy 30 authentication pre-share
isakmp policy 30 encryption 3des
isakmp policy 30 hash md5
isakmp policy 30 group 2
isakmp policy 30 lifetime 43200


i notice in the crypto map for 30 there is a KB defined as part of the lifetime, but no such setting in the wrvs4400. i removed it at one point manually in the pix and rebuilt the crypto map, but that did not affect things.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion

Related Content