Browse Source

strongswan: start charon directly from swanctl

ipsec uses starter, and reads /etc/ipsec.conf (which then includes
/var/ipsec/ipsec.conf, etc). This is overly complicated, and can
be problematic if you're using both swanctl and ipsec for migration.

Running charon directly from procd via the init.d script avoid
all of this.

Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
lilik-openwrt-22.03
Philip Prindeville 4 years ago
parent
commit
a783986cbc
2 changed files with 3 additions and 3 deletions
  1. +1
    -1
      net/strongswan/Makefile
  2. +2
    -2
      net/strongswan/files/swanctl.init

+ 1
- 1
net/strongswan/Makefile View File

@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk
PKG_NAME:=strongswan
PKG_VERSION:=5.9.2
PKG_RELEASE:=7
PKG_RELEASE:=8
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
PKG_SOURCE_URL:=https://download.strongswan.org/ https://download2.strongswan.org/


+ 2
- 2
net/strongswan/files/swanctl.init View File

@ -4,7 +4,7 @@ START=90
STOP=10
USE_PROCD=1
PROG=/usr/lib/ipsec/starter
PROG=/usr/lib/ipsec/charon
. $IPKG_INSTROOT/lib/functions.sh
. $IPKG_INSTROOT/lib/functions/network.sh
@ -614,7 +614,7 @@ start_service() {
procd_open_instance
procd_set_param command $PROG --daemon charon --nofork
procd_set_param command $PROG
procd_set_param file $SWANCTL_CONF_FILE
procd_append_param file /etc/swanctl/conf.d/*.conf


Loading…
Cancel
Save