I'll will create a patch that proposes a fix. I found out that
strongswan always need either charon (enable-charon option) or
charon-systemd(enable-systemd option). So the bug was that both were
disabled when using swanctl without systemd.
/Lars Pedersen.
On Mon, 17 Feb 2020 at 11:19, Michael Olb
On Mon, Feb 03, 2020 at 09:38:20AM +0100, Lars Pedersen wrote:
> On Sat, 1 Feb 2020 at 07:47, Michael Olbrich wrote:
> > > +ifdef PTXCONF_STRONGSWAN_SWANCTL
> > > + @$(call install_lib, strongswan, 0, 0, 0644, libvici)
> > > + @$(call install_tree, strongswan, 0, 0, -, /etc/strongswan.d)
>
On Sat, 1 Feb 2020 at 07:47, Michael Olbrich wrote:
> > +ifdef PTXCONF_STRONGSWAN_SWANCTL
> > + @$(call install_lib, strongswan, 0, 0, 0644, libvici)
> > + @$(call install_tree, strongswan, 0, 0, -, /etc/strongswan.d)
> > + @$(call install_alternative, strongswan, 0, 0, 0644,
> > /etc
On Mon, Jan 13, 2020 at 01:55:12PM +0100, Lars Pedersen wrote:
> Add swanctl support which replaces the old starter, ipsec and stroke
> backend. Swanctl is only tested with systemd.
> https://wiki.strongswan.org/projects/strongswan/wiki/Charon-systemd
>
> Signed-off-by: Lars Pedersen
> ---
> v3:
Add swanctl support which replaces the old starter, ipsec and stroke
backend. Swanctl is only tested with systemd.
https://wiki.strongswan.org/projects/strongswan/wiki/Charon-systemd
Signed-off-by: Lars Pedersen
---
v3:
- Removed unnecessary configuration options
- Install/enable strongswan syste
