> Shouldn't a VPN plugin be able to simply pass, for example, the actual device over which the VPN connection is established as TUNDEV rather than a tun device?
No, this doesn't seem to work, as NM does some changes to that interface, breaking things completely. Passing "lo" seems to work, though. You may try the attached (second) patch (against strongSwan itself, version 4.5.2). The first patch fixes another issue that we fixed some time ago upstream. While this might work as a work-around for now, I don't think this is an ideal solution. For the long term, we have our own tundev based backend in the pipeline that should work much better with NM. ** Patch added: "0001-Fix-initialization-of-NM-plugin.patch" https://bugs.launchpad.net/ubuntu/+source/network-manager-strongswan/+bug/872824/+attachment/3203670/+files/0001-Fix-initialization-of-NM-plugin.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872824 Title: Network-manager locks up when adding strongSwan VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-strongswan/+bug/872824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
