Re: How to setup NetworkManager-openconnect?



Hi Thomas,

Thank you for all the details you have provided, I am sure they will
help.

My suspicion was (and is now re-inforced after reading your response)
that I have mis-installed the plugin.   NetworkManager is installed
under /usr while NetworkManager-openconnect is under /usr/local.  I did
ensure the /usr/local/lib is set in the ld.so.conf and refreshed with
ldconfig.  Nonetheless I still do not get to see any option(s) from the
nm-connection-editor to add an openconnect connection type.  I only see
the Hardware and Virtual lists.  I will try to re-install and push the
NetworkManager-openconnect to /usr.

To answer your last question--I am under Slackware-current and there is
no appropriate package for openconnect plugin for the version I am on
for NetworkManager.  Hence, why I build from source.

I 'll let you know how it goes--in the meantime my GF will have to use
the terminal lol.  She is very happy with NetworkManager and nm-applet
though :)

Cheers,
George

On Sat, Apr 2, 2016, at 11:07 AM, Thomas Haller wrote:
On Sat, 2016-04-02 at 08:27 -0400, George Karabotsos wrote:
Hello all,

I have NetworkManager with nm-applet working on my linux-box.  I have
openconnect installed and working. 

I downloaded the source version of NetworkManager-openconnect
compiled
it and installed it succesfully.  Unfortunately, I can't find any
documentation or howto on how to configure it.  Would anyone have
such
documentation or even a working configuration file should be able to
get
going.

My other question is how will I then setup VPN from nm-applet--I did
see
the dialogs for VPN but I cannot identify what I need to configure.

Here's some background: for the longest time I have been using
wpa_supplicant, dhcpcd, and openconnect to hook up to the net and my
work's vpn. I would like to make it a little more "user friendly" so
that my GF can hook up my desktop to the net and her employer's VPN.

Hi George,


I never used openconnect or nm-openconnect, but to answer in principle:


with the NetworkManager VPN plugins, they provide a plugin that can be
loaded via nm-connection-editor and gnome-control-center. So, that is a
convenient way to configure them.

For KDE/plasma-nm, I think they implement UI support also in form of
separate plugins, so maybe you will find a different plugin there
(those plugins live in a separate package and source repository -- if
it exists for openconnect).


(of course, you could also configure a connection manually via nmcli or
by editing the file in /etc/NetworkManager/system-connections). That
doesn't need UI support. There is no documentation about that beside
the source code 
https://git.gnome.org/browse/network-manager-openconnect/tree/src/nm-op
enconnect-service.c?h=nm-1-0#n358
Also, the import-code makes it pretty clear which properties are
supported: https://git.gnome.org/browse/network-manager-openconnect/tre
e/properties/nm-openconnect.c?h=nm-1-0#n119
But probably you don't want to do that.


As you say, you tried to use nm-applet (and it's sibling nm-connection-
editor). So, just start nm-connection-editor and click "Add" and select
openconnect VPN. Alternatively, if you have a openconnect
configuration, you might choose "Import a saved VPN connection".
Doesn't that work? Then maybe you did something wrong and nm-
connection-editor cannot find the plugin. When you start the editor in
the terminal, do you see a helpful message there?
If you use 1.0.10 NetworkManager, you must also use nm-openconnect <=
1.0, but I guess you did that -- as master branch wouldn't compile.


On Fedora, there is also a package NetworkManager-openconnect which
provides the UI plugin for nm-connection-editor. Why do you build from
source?



Thomas




Cheers,
George

PS: my system specifics
bash-4.3# uname -a
Linux montreal 4.4.6 #2 SMP Wed Mar 16 14:17:03 CDT 2016 x86_64
Intel(R)
Core(TM) i7 CPU M 620 @ 2.67GHz GenuineIntel GNU/Linux

bash-4.3# NetworkManager --version
1.0.10

bash-4.3# openconnect --version
OpenConnect version v7.06
Using GnuTLS. Features present: PKCS#11, HOTP software token, TOTP
software token, System keys, DTLS
Email had 1 attachment:
+ signature.asc
  1k (application/pgp-signature)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]