[Bug 256508] security/strongswan: ipsec.conf never loaded
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 256508] security/strongswan: ipsec.conf never loaded"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 256508] security/strongswan: ipsec.conf never loaded"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 256508] security/strongswan: ipsec.conf never loaded"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 09 Jun 2021 19:14:38 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256508
Bug ID: 256508
Summary: security/strongswan: ipsec.conf never loaded
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs@FreeBSD.org
Reporter: ohartmann@walstatt.org
CC: strongswan@Nanoteq.com
CC: strongswan@Nanoteq.com
Flags: maintainer-feedback?(strongswan@Nanoteq.com)
I have to admit that I'm new to IPsec and StrongSwan. The subject is FreebSD
13-STABLE (FreeBSD 13.0-STABLE #159 stable/13-n245920-95b7e4e0feb: Mon Jun 7
12:03:41 CEST 2021 amd64) and recent port security/strongswan
(strongswan-5.9.2_2 ).
The setup I use has been tested for good on a Linux Xubunto box 21.04
(ipsec.conf) so far by editing and preparing the ipsec.conf and ipsec.secrets
files, for FreeBSD's port located at /usr/local/etc. FreeBSD box is a client
and should contact a network behind an AVM Fritz!Box router with a configured
IPsec VPN.
Whe starting strongswan or restarting strongswan it seems that
/usr/local/etc/ipsec.conf never is read or does never configure any VPN:
# service strongswan restart
Stopping strongswan.
Starting strongswan.
no files found matching '/usr/local/etc/swanctl/conf.d/*.conf'
no authorities found, 0 unloaded
no pools found, 0 unloaded
no connections found, 0 unloaded
It is also remarkable that the files
strongswan.d/starter.conf
strongswan.d/charon/stroke.conf
contain an unsubstituted variable "${sysconfdir}" which seems to stay
unsubstituted while ipsec starts up - I might be wrong.
--
You are receiving this mail because:
You are the assignee for the bug.