danfruehauf
not working in Ubuntu 16.04
The plugin send this error:
** Message: vpn: (ssh,/etc/NetworkManager/VPN/nm-ssh-service.name) cannot load legacy-only plugin
@lhw is kindly packaging this for Ubuntu. Ideally that should be reported upstream.
Just now I merged #53 which may or may not fix that problem. Care to test it?
Yeah; the nm 1.2 branch indeed adds a "non-legacy" plugin.
We just discovered one problem that has to do with the unfortunate timing of Ubuntu and NM releases; the snapshot that's present in Ubuntu 16.04 requires absolute paths to VPN plugins (which would likely make lintian unhappy). On Ubuntu 16.04 you need to configure the plugin with --enable-absolute-paths.
I'll try to get in touch with the Ubuntu maintainers to see what can be done about updating the network-manager package. There's a couple more fixes they may want to pick up.
(tagging @lhw as this is something he might be interested in.)
I'm currently in the process of updating the package in debian so that it works with 1.2 as the version has now landed in unstable. But the ubuntu package is a bit of an issue. They froze the update just so that a nm-ssh depends on an older version of nm in the repo. I'm gonna have a look if we can put up a fix for that or otherwise remove the version all together from 16.04. Sad for a LTS release but better than having a broken version in the repos.
A note in general. It's probably best to use the distribution bug trackers for these kind of issues. They are somewhat unrelated to the project and I don't get notified unless the project maintainers tag me in the bug report.
@danfruehauf Do you think it is possible to get 0.9.4 to work with the 1.2rc they froze in 16.04? The absolute-path option is not yet available in the plugin version. I assume it's going to require a larger patch set to get this to work unless there is a quick and dirty patch to ignore the changes.
If so I'll try to get the new debian release in. That one should build with 1.2rc1 in 16.04. If not I'll request they remove the package so you won't get spammed with bug reports.
Hi all,
I am trying to use nm-ssh-1.2 (from https://mentors.debian.net/package/network-manager-ssh) Ubuntu 16.04. It builds and installs without a problem but when connection is activated, NM informs about a connection error and nothing useful appears in syslog. No actual connection is seen on the other end and nm-ssh-service is left running after the attempt.
I attempted to "pre-start" the plugin with --debug but the only output I get is: "*** Message: nm-ssh-service (v1.2.0) starting..."
Any suggestions on how to continue the debug?
@danfruehauf Do you think it is possible to get 0.9.4 to work with the 1.2rc they froze in 16.04? The absolute-path option is not yet available in the plugin version. I assume it's going to require a larger patch set to get this to work unless there is a quick and dirty patch to ignore the changes.
Not sure about that. I haven't been completely on top of things with the latest nm changes. @lkundrak has kindly contributed all the necessary patches for those.
@eugenesan See the debugging section - https://github.com/danfruehauf/NetworkManager-ssh#debugging
What you want to do is start it as you did, with --debug, then start a connection. If you started it as root, then it should spew the log to stdout/stderr over there. Let me know how you go...
@danfruehauf Running the service with --debug doesn't help, NM spawns it's own copy of the service and ignores the one invoked manually.
This is what is shown in syslog:
May 11 10:02:42 myhost NetworkManager[692]: <info> [1462975362.6805] audit: op="connection-activate" uuid="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" name="VPN connection 1" pid=2102 uid=1000 result="success"
May 11 10:02:42 myhost NetworkManager[692]: <info> [1462975362.6891] vpn-connection[0x248b3c0,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,"VPN connection 1",0]: Started the VPN service, PID 2804
May 11 10:02:47 myhost NetworkManager[692]: <warn> [1462975367.6740] vpn-connection[0x248b3c0,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,"VPN connection 1",0]: Timed out waiting for the service to start
May 11 10:02:47 myhost NetworkManager[692]: (nm-exported-object.c:930):nm_exported_object_dispose: code should not be reached
@lhw I see that Ubuntu 16.04 LTS now has network-manager-ssh 1.2.0. Does that fix this issue and the Ubuntu bug?
It's been so long since i worked on this, can't even remember the reason for the bugs. I will have to check later. If it does work I will close the bug reports later. If not I'll look into fixing this again.
1.2.0 should work with 16.04 as I fixed most of the bugs before I imported 1.2.1 which had them built-in. I might spin up a VM in the near future and test. But Ubuntu wasn't really a priority for me.
What version of nm is shipped with Ubuntu 16.04?
I reckon the new 1.2.6 version should work with any newer version of nm. Speaking of which, upstream maintainers were actually quite upset they have broke compatibility with this plugin. However, I got to fix it as soon as I could.
In general, it'll be much easier for me to test this plugin now as I have a dedicated AWS VM just for that.
See https://phabricator.kde.org/D14035. Note that OpenSSH 7.7 packaged in Debian testing currently has broken tun/tap support due to https://bugzilla.mindrot.org/show_bug.cgi?id=2855.
