<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Tim , <BR> I did not see the rightsubnet and leftsubnet listed in your ipsec configuration. It is possible that you have a mismatch between what you have for your leftsubnet/rightsubnet and what Cisco side has for its access-list 127 ( which is a translation of {local subnet} { remote subnet } )<br><BR><br><BR><br><span style="font-family:Tahoma,Helvetica,Sans-Serif;font-style:italic;font-weight:bold">-<span style="font-family:Times New Roman,Times,Serif"> Simon Charles - </span></span><br><br><br><div><hr id="stopSpelling">Date: Wed, 19 Mar 2014 09:52:12 -0700<br>From: tim@mccune.name<br>To: users@lists.openswan.org<br>Subject: [Openswan Users] Connecting to Cisco VPN, getting INVALID_ID_INFORMATION followed by "perhaps peer likes no proposal"<br><br><div dir="ltr"><div><div><div><div><div><div>Hi there. I was wondering if anyone could help me out with this problem I'm having trying to connect from openswan 2.6.38 on Ubuntu Lucid to a Cisco VPN appliance. I don't seem to be able to establish a connection. Here is the output I get in pluto.log:<br>
<br>"mine" #1: initiating Main Mode<br>"mine" #1: ignoring Vendor ID payload [Cisco IKE Fragmentation]<br>"mine" #1: transition from state STATE_MAIN_I1 to state STATE_MAIN_I2<br>"mine" #1: STATE_MAIN_I2: sent MI2, expecting MR2<br>
"mine" #1: received Vendor ID payload [Cisco-Unity]<br>"mine" #1: received Vendor ID payload [XAUTH]<br>"mine" #1: ignoring unknown Vendor ID payload [716e44df1a91b4edaffa5ff96dd22125]<br>"mine" #1: ignoring Vendor ID payload [Cisco VPN 3000 Series]<br>
"mine" #1: transition from state STATE_MAIN_I2 to state STATE_MAIN_I3<br>"mine" #1: STATE_MAIN_I3: sent MI3, expecting MR3<br>"mine" #1: received Vendor ID payload [Dead Peer Detection]<br>"mine" #1: Main mode peer ID is ID_IPV4_ADDR: 'XX.XX.XX.XX'<br>
"mine" #1: transition from state STATE_MAIN_I3 to state STATE_MAIN_I4<br>"mine" #1: STATE_MAIN_I4: ISAKMP SA established {auth=OAKLEY_PRESHARED_KEY cipher=aes_128 prf=oakley_sha group=modp1024}<br>"mine" #2: initiating Quick Mode PSK+ENCRYPT+TUNNEL+PFS+UP+IKEv2ALLOW+SAREFTRACK {using isakmp#1 msgid:c359ad28 proposal=AES(12)_128-SHA1(2)_160 pfsgroup=OAKLEY_GROUP_MODP1024}<br>
"mine" #1: ignoring informational payload, type INVALID_ID_INFORMATION msgid=00000000<br>"mine" #1: received and ignored informational message<br>"mine" #1: received Delete SA payload: deleting ISAKMP State #1<br>
packet from <a href="http://80.87.94.106:500" target="_blank">80.87.94.106:500</a>: received and ignored informational message<br>"mine" #2: max number of retransmissions (2) reached STATE_QUICK_I1. No acceptable response to our first Quick Mode message: perhaps peer likes no proposal <br>
"mine" #2: starting keying attempt 2 of an unlimited number<br><br></div>and this output just repeats over and over. As far as I can tell, we are sending all of the correct parameters in our proposal, based on the configuration information we have been given by the organization that maintains the Cisco appliance. Here is what they provided us with:<br>
<br></div><div>Phase 1:<br></div>Encryption scheme: IKE<br>Authentication Method: Pre-Shared Key<br></div>Diffie-Hellman Group: Group 2<br></div>Encryption Algorithm: AES128<br></div>Hashing Algorithm: SHA-1<br></div>Main or Aggressive Mode: Main Mode<br>
Lifetime (for renegotiation): 28800 seconds<div><div><div><div><br></div><div>Phase 2:<br></div><div>Encapsulation mode: tunnel<br></div><div>Encryption algorithm ESP: AES128<br></div><div>Authentication Algorithm: SHA-1<br>
</div><div>Perfect Forward Secrecy: Group 2<br>Lifetime (for renegotiation): 3600 seconds<br><br></div><div>Here is the configuration on our end in ipsec.conf:<br><br>conn mine<br> left=XX.XX.XX.XX<br> right=XX.XX.XX.XX<br>
authby=secret<br> auto=start<br> ike=aes128-sha1;modp1024<br> phase2=esp<br> phase2alg=aes128-sha1;modp1024<br> pfs=yes<br> aggrmode=no<br> salifetime=28800s<br><br><br></div><div>And here is the configuration on their end on the Cisco appliance:<br>
<br>crypto ipsec transform-set MyOrg esp-aes esp-sha-hmac<br>crypto map gtvpn-rules 127 match address 127<br>crypto map gtvpn-rules 127 set pfs group2<br><br>crypto map gtvpn-rules 127 set peer XX.XX.XX.XX<br>crypto map gtvpn-rules 127 set transform-set MyOrg<br>
crypto map gtvpn-rules 127 set security-association lifetime seconds 3600<br><br>tunnel-group XX.XX.XX.XX type ipsec-l2l<br>tunnel-group XX.XX.XX.XX ipsec-attributes<br>pre-shared-key xxxxxxxx<br><br>access-list 127 extended permit ip host YY.YY.YY.YY host XX.XX.XX.XX<br>
access-list 127 extended permit ip host ZZ.ZZ.ZZ.ZZ host XX.XX.XX.XX<br><br></div><div>Any guidance would be appreciated.<br><br>Thank you!!<br></div></div></div></div></div>
<br>_______________________________________________
Users@lists.openswan.org
https://lists.openswan.org/mailman/listinfo/users
Micropayments: https://flattr.com/thing/38387/IPsec-for-Linux-made-easy
Building and Integrating Virtual Private Networks with Openswan:
http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155</div> </div></body>
</html>