The built-in Windows VPN client uses IKEv1 (strongSwan attempts to use IKEv2 by
default), so add:
keyexchange=ikev1
to your options and you should now see it being caught in your pluto.log (pluto
is the IKEv1 daemon, charon is for IKEv2).
-a
On Oct 4, 2011, at 5:13 PM, Tristan Ball wrote:
>
On Mon, Oct 3, 2011 at 6:10 AM, Tobias Brunner wrote:
> Hi Diego,
>
>>>
>>>
>>>
>> I forgot to clarify that route is inserted if compress=no. In
>> kernel_netlink_ipsec.c add_policy methed, the code checks if mode !=
>> MODE_TRANSPORT to insert to route.
>
> Yes, if IPComp is e
Thanks Ariel.
With that tip and a little more fiddling, I've gotten it to work. However I'm
now stuck behind the issue that I can't have more than one client behind a
single NAT firewall. Google and the mailing list archives seem to say that
this is a known issue with no current publicly avail
Hello Tristan,
The Windows 7 Agile VPN client has great IKEv2 support which allows
the installation of a virtual IP via the IKEv2 configuration payload.
Please have a look at our Win7 <-> strongSwan HOWTO:
http://wiki.strongswan.org/projects/strongswan/wiki/Windows7
Kind regards
Andreas
On 10/
Thanks Andreas.
Yes, I saw that - and I'll probably use that functionality for a separate set
of requirements. Unfortunately for this particular instance, the customer has
decreed "No VPNs" - I think partly for support reasons within their own
organisation.
Which is why I was hoping to use the
