On 1 June 2016 at 10:16, Patrick Wildt wrote:
> Hi,
>
> Currently there is only one address pool which is either v4 or v6.
> This means that we cannot have dual-stack VPNs via iked. Clients
> then might tunnel all IPv4 traffic, but IPv6 traffic is still using
> the non-encrypted default route, wh
Hi,
Currently there is only one address pool which is either v4 or v6.
This means that we cannot have dual-stack VPNs via iked. Clients
then might tunnel all IPv4 traffic, but IPv6 traffic is still using
the non-encrypted default route, which might be a security issue.
To enable dual-stack IKEv2,
The following provides address pools for iked. It's nothing fancy, but
it seems to work, at least in the cursory testing done against the
Windows 7 client.
Each policy gets it's own pool, configured by "config address - ".
There is a hard limit of 65536 addresses (8kb) per pool, which should be p
You can use "cvs add" against a mirror to add files. Directories
require write access, so that won't work. Then use "cvs diff -Nup" to
include all of the (N)ew files.
tech@ is the preferred mailing list for diffs.
On 2013 Jun 05 (Wed) at 23:23:53 -0600 (-0600), Ryan Slack wrote:
:I wish to sub
I wish to submit a working implementation of address pools for iked,
however as it's my first real code contribution and has 643 lines
(mostly patch context) I'm wondering if posting here is the correct
channel.
Also, what is the preferred/normal way to include new files in a patch?
--Ryan Slack
