Re: [strongSwan] Does windows 7 clients work well with l2tp/ipsec using strongswan?

Hi, I didnt try much to find the exact suitable mtu . And I only adjust the default win7 vpn mtu (which is at the client side) from 1400 down to 1300 and problem got fixed. 2012/4/17 Morgan Yang > Hi Morgan: > > Did you have to decrease the MTU of the VPN interface? Was this the MTU on > y

[strongSwan] Questions on Strongswan

Hi, I have some questions regarding the usage of strongswan for which I could not find any answers. Could some body please reply if you have answers to any of these questions ? Thanks & Regards, Nagaraj 1: Is a fallback to IKEv1 supported when IKEv2 does not succeed with a remote peer ? 2: Is

[strongSwan] Problem routing traffic to Public IP via Tunnel

Hi, I have problem reaching a public IP over ipsec tunnel. The first tunnel that I configured uses a private IP for the rightsubnet and everything works OK, but when I added a public IP on the rightsubnets= list it doesn't. There seems to be no traffic coming to the other side of the tunnel. The c

Re: [strongSwan] help: ping behaviour when tunnel is not established

Hello, Any insight to the below would be helpful. Regards, -sanjay From: users-bounces+sanjay.shukla=ipc@lists.strongswan.org [mailto:users-bounces+sanjay.shukla=ipc@lists.strongswan.org] On Behalf Of Shukla, Sanjay Sent: Friday, April 13, 2012 3:58 PM To: users@lists.strongswan.org Su

Re: [strongSwan] Does windows 7 clients work well with l2tp/ipsec using strongswan?

Hi, finally i got it solved by lowering the mtu of the vpn interface.hope it helps some one meeting the same problem as me. 2012/4/13 Morgan > Hi, >Recently i set up vpn on vps with ubuntu 11.10. I have configured > l2tp/ipsec using strongswan. > I tested the vpn by ios/android/win7 behi

Re: [strongSwan] soft lifetime for inbound and outbound SA

Hi Divya, >>From strongswan-4.3.6/src/charon/ sa/child_sa.c, in function install: > > -- > if (!lifetime->time.jitter && !inbound) > { /* avoid triggering multiple rekey events */ > lifetime->time.rekey = 0;

Re: [strongSwan] Ping is not working after establishing a tunnel in strongswan

Hi Tobias, Thanks for your nice reply. I get back on you for further doubts on this. Regards, Saravanan N On Mon, Apr 16, 2012 at 2:50 PM, Tobias Brunner wrote: > Hi Saravanan, > > > I have established a VPN tunnel between GW and VPN server using > > Strongswan. > > Is the tunnel between t

[strongSwan] soft lifetime for inbound and outbound SA

Hi, I found this information from https://lists.strongswan.org/pipermail/users/2012-April/007415.html >> Since the in- and outbound IPsec SA are rekeyed together only one of them >> needs to trigger it >> (hard lifetimes are installed for both SAs to ensure they are deleted once >> they expire)

Re: [strongSwan] strongswan and playbook issues

Hi Dan, > After fixing the simple issue i had originally had i get a little bit > farther in the process but im still receiving an authentication error on > my playbook. Are there any more details about the error on the PlayBook? Some logs perhaps? From the point of view of strongSwan the con

Re: [strongSwan] Ping is not working after establishing a tunnel in strongswan

Hi Saravanan, > I have established a VPN tunnel between GW and VPN server using > Strongswan. Is the tunnel between those two hosts intended as host-host tunnel or as host-net tunnel? What did you configure for left|rightsubnet? If your SPD entries are any indication it seems you configured rig

Re: [strongSwan] IPSec PKI error

Hi Chris, > Strongswan 4.3.xx on SLES11 SP1. > ... > when I run IPSec pki --gen >> cakey.der I get unknown IPSec command > 'pki'. IPSec is started. What is the problem? The ipsec pki command was introduced with 4.3.5, so depending on the value of .xx in the version number above, it won't be avail

Re: [strongSwan] Regarding Certificate based authentication ( Load Tests )

Thanks for the information Rajiv, As per my previous post i had followed the same steps but with different names right ? Its not working for me :( . Also u have told to copy the responder_key.pem to responder side. Which means we are SHARING A PRIVATE KEY which should not be done ri