I wasn't able to reproduce issue from the command-line with NetworkManager-l2tp, it only happens after NetworkManager-l2tp restarts strongSwan under NetworkManager.
Turns out it is the same NetworkManager issue as the following : https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1244157/comments/7 I used the attached patch for : /etc/apparmor.d/usr.lib.ipsec.charon /etc/apparmor.d/usr.lib.ipsec.stroke -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587886 Title: strongswan ipsec status issue with apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1587886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
