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 running strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf it's both safe and enough to disable strongswan.service and leave enabled just strongswan-swanctl.service? Thank you. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1883074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
