Ok, I also tested the yakkety case as described in comment #36 - that is really a good way to reproduce with a less complex setup. ALso thank you all for your participation in testing with the more complex cases.
So for Xenial: - VPN can be established with the fix - ipsec status fixed - Apparmor DENIES fixed Fo Yakkety - l2tp case apparmor DENIES fixed (connection itself sometimes worked before) - ipsec status fixed And along that no general regression found. That said setting verification-done. ** Tags removed: verification-needed ** Tags added: verification-done verification-done-xenial verification-done-yakkety -- 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/hundredpapercuts/+bug/1587886/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
