<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><div>Thanks for reply!</div><div><br></div><div>>What version of openswan is this?</div><div> openswan version: 2.6.28.</div><div><br></div><div>>strongswan 4.0.7 seems old?</div><div> Maybe the strongswan is too old. But I can connect to the vpn in Windows.</div><div><br>--- On <b>Tue, 8/31/10, Paul Wouters <i><paul@xelerance.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Paul Wouters <paul@xelerance.com><br>Subject: Re: [Openswan Users] Can't connect to VPN Server<br>To: "Adam Wu" <airhello@ymail.com><br>Cc: users@openswan.org<br>Date: Tuesday, August 31, 2010, 5:10 PM<br><br><div class="plainMail">On Tue, 31 Aug 2010, Adam Wu wrote:<br><br>> I install the openswan in Linux, and connect to the VPN Server but fail.<br>> What
is wrong with it?<br>> The connect message is:<br>> 002 "wan" #1: initiating Main Mode<br>> 104 "wan" #1: STATE_MAIN_I1: initiate<br>> 003 "wan" #1: ignoring Vendor ID payload [strongSwan 4.0.7]<br><br>Looks like the remote peer is strongswan<br><br>> 002 "wan" #1: transition from state STATE_MAIN_I2 to state STATE_MAIN_I3<br>> 108 "wan" #1: STATE_MAIN_I3: sent MI3, expecting MR3<br>> 003 "wan" #1: next payload type of ISAKMP Hash Payload has an unknown value: 217<br>> 003 "wan" #1: malformed payload in packet<br>> 002 "wan" #1: sending notification PAYLOAD_MALFORMED to 202.118.7.98:4500<br>> 003 "wan" #1: discarding duplicate packet; already STATE_MAIN_I3<br><br>This could be a bug in strongswan, or perhaps a mismatched PSK?<br><br>What version of openswan is this? If it is a recent openswan (eg 2.4.15 or<br>2.6.2x) then the openswan side should be fine.<br><br>strongswan 4.0.7 seems old? Perhaps upgrade that end
first?<br><br>Paul<br></div></blockquote></div></td></tr></table><br>