Replies: 1 comment 2 replies
-
Usually the strongSwan
IPsec connections are managed by the |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I have been using Strongswan for many years now, and all is working great using the "old" ipsec model of commands. Recently I saw that the command set is moving to the new "modern" style (even though I dont know why as the current one that I am using is working so well and reliable) I am unable to get it to start, or I am missing something?
Currently and what I am using right now, you need /etc/ipsec.conf, /etc/ipsec.secrets configured properly and execute /usr/sbin/ipsec start and boom you are up and running in no time!
With the new set of commands, I have converted my current /etc/ipsec.conf and /etc/ipsec.secets to the new style /etc/swanctl/conf.d/swanctl.conf. The main question is...How do you start it? What is the replacement for "ipsec start" ? I have been looking through documentation and nowhere was mentioned (except the use of systemd - not all systems have systemd and I dont even know what it is)? Am I missing something?
Once you remove /etc/ipsec.conf and /etc/ipsec.secrets the command "ipsec start" will no longer work as it is looking for the "old" files.
/usr/sbin/swanctl with any options gives me connection refused (Because the daemon is not running).
I am running Slackware Linux 15.0 - Slackware does not have systemd.
I appreciate any help!
Beta Was this translation helpful? Give feedback.
All reactions