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
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 : /bugs.launchpad .net/ubuntu/ +source/ apparmor/ +bug/1244157/ comments/ 7
https:/
I used the attached patch for : apparmor. d/usr.lib. ipsec.charon apparmor. d/usr.lib. ipsec.stroke
/etc/
/etc/