Tunnels in LibreSwan and OpenSwan allow for many options to be set on a
per tunnel basis. Pass through any options starting with ipsec_ to the
connection in the configuration file. Administrators are responsible for
picking valid key/value pairs.
Signed-off-by: Andreas Karis
---
Documentation/tu
On Wed, Mar 2, 2022 at 8:40 AM Andreas Karis wrote:
>
> Tunnels in LibreSwan and OpenSwan allow for many options to be set on a
> per tunnel basis. Pass through any options starting with ipsec_ to the
> connection in the configuration file. Administrators are responsible for
> picking valid key/va
On 3/2/22 14:40, Andreas Karis wrote:
> Tunnels in LibreSwan and OpenSwan allow for many options to be set on a
> per tunnel basis. Pass through any options starting with ipsec_ to the
> connection in the configuration file. Administrators are responsible for
> picking valid key/value pairs.
>
> S
Hi!
No worries! After some reflection, the '--force-encapsulation' patch IMO is
not the correct way to go, but I did not know how to recall it once it was
acknowledged ... :-(
I would prefer to have the patch that allows the generic options instead,
so that 'options:ipsec_encapsulation=yes' can be
On 4/26/22 14:31, Andreas Karis wrote:
> Hi!
>
> No worries! After some reflection, the '--force-encapsulation' patch IMO is
> not the correct way to go, but I did not know how to recall it once it was
> acknowledged ... :-(
Acknowledged doesn't mean accepted. :)
In any case, the procedure is t
On 3/18/22 16:08, Mike Pattrick wrote:
> On Wed, Mar 2, 2022 at 8:40 AM Andreas Karis wrote:
>>
>> Tunnels in LibreSwan and OpenSwan allow for many options to be set on a
>> per tunnel basis. Pass through any options starting with ipsec_ to the
>> connection in the configuration file. Administrato