Tobias, thank you!
** Changed in: strongswan (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883074
Title:
After system reboot conn fails until swanctl restart
Yeah, I think disabling strongswan.service should be enough. If you
want to make sure, uninstall the strongswan-starter package (unless you
need the pool utility, which is contained in that package for some
reason).
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Hi Tobias,
I'm not using ipsec.conf, just swanctl.conf
Do you mean, that having this configuration:
root@newton:~# systemctl |egrep -i "swan|charon"
strongswan-swanctl.service loaded active running strongSwan IPsec IKEv1/IKEv2
daemon using swanctl
strongswan.service loaded active runn
In 18.04, strongswan.service is the legacy systemd unit that controls
starter/charon and loads configuration from ipsec.conf. The strongswan-
swanctl.service unit instead controls the charon-system daemon and is
configured via swanctl.conf, which the unit loads via `swanctl --load-
all` automatica
