[strongSwan] ANNOUNCE: strongswan-5.2.0 released

Hi, we are proud to announce the release of strongSwan 5.2.0 which offers a native port to Windows 7/8 and many other new features. For specifics read our blog entry: http://www.strongswan.org/blog/2014/07/09/strongswan-5.2.0-released.html or browse the detailed changelog:

Re: [strongSwan] libipsec/net2net-cert: Ipsec tunnel UP but decrypted traffic does not reach beyond GW: /etc/updown: no such file or directory

Hi Noel, Thank you for your reply. I have compiled with the option you specified and now I don't see the '/etc/updown: no such file or directory' in the log But still the behaviour is same i,e iptables rules are not populated. Rather flow in opposite direction is quite odd. To make sure my

[strongSwan] Small Problems with 5.2

Hi, I hit two problems after upgrading to 5.2. System on both sides is a Debian wheezy 64. Strongswan compiled with: [client] ./configure --prefix=/usr --sysconfdir=/etc --enable-blowfish --enable-curl --enable-openssl --disable-ikev1 --enable-ntru [gateway] ./configure --prefix=/usr

Re: [strongSwan] Small Problems with 5.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Dirk, Can you please provide your strongswan.conf? Regards, Noel Kuntze GPG Key id: 0x63EC6658 Fingerprint: 23CA BB60 2146 05E7 7278 6592 3839 298F 63EC 6658 Am 10.07.2014 15:54, schrieb Dirk Hartmann: Hi, I hit two problems after

Re: [strongSwan] Random IPSEC IKE1 Dropping

Can anyone help me out with this issue? I know I have very few details to go off of, but at this point, I don't know what else is needed and what needs to be provided. Thanks, Brad From: Turnbough, Bradley E. Sent: Wednesday, July 09, 2014 9:00 AM To:

Re: [strongSwan] Random IPSEC IKE1 Dropping

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Bradley, Without a log file, I can only assume, that the tunnel gets torn down, because the communication to the peers get severed. I propose enabling dpd with dpdaction=restart, as well as closeaction=restart, so the tunnel gets