charon-nm never terminated

[Maxxer]

I'm trying to connect to my pfSense's strongswan server, sadly the connection fails, but the problem is that nm's underlying process, charon-nm, is never terminated, and keeps going until killed.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager-strongswan 1.3.0-2
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 5 08:43:23 2015
InstallationDate: Installed on 2015-04-04 (30 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
SourcePackage: network-manager-strongswan
UpgradeStatus: No upgrade log present (probably fresh install)

[Tobias Brunner (tobias-strongswan)]

Your connection fails because you haven't checked the "Request an inner IP address" checkbox but configured an IP address pool in `rightsourceip` on the server (which is required if your client is behind a NAT). So change your connection settings so a virtual IP is requested from the server.

Regarding charon-nm not terminating, that's due to a change in NM 0.9.10 [1]. In older releases a SIGTERM was sent to the process, now it's up to the service to hook the "quit" signal sent by NM and terminate itself if needed.

However, I'm not sure if it's actually a problem. charon-nm has not changed the routing or installed any IPsec SAs yet (due to the error) so it should be possible to just start the connection again with the same instance of charon-nm still running (after fixing the config, of course). And if the connection is terminated properly, reusing the same instance should also be OK. I haven't tested this though, so it's possible that charon-nm doesn't handle this correctly (terminating the process via "quit" signal would be quite simple to implement though).

Just so you know, strongSwan's NM plugin is pretty out-of-date and not fully compatible with current NM releases.

[1] http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/src/vpn-manager/nm-vpn-service.c?id=4b57f6920e9a4dda7dcabaa46e0c6b693c9af83c

[Maxxer (lorenzo-milesi)]

thanks for the clarification, indeed checking the checkbox established the connection.

about the process, my concern was that since the connection is not established there's a pending process around. if the user doesn't fix the connection, what will happen to it?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.