From: divan@santanas.co.za
To: Jelle Licht <jlicht@fsfe.org>, Help guix <help-guix@gnu.org>
Subject: Re: network-manager-openconnect setup - [External Email]
Date: Mon, 09 Sep 2019 22:01:42 +0200 [thread overview]
Message-ID: <871rwpqlwv.fsf@fnb.co.za> (raw)
In-Reply-To: <87v9v4wwy2.fsf@jlicht.xyz>
>> Trying to use it, after I installed it system wide and rebooted I get
>> this;
>>
>> ~ á… sudo nmcli con up vpn-fnb --ask
>> Error: Connection activation failed: The VPN service 'org.freedesktop.NetworkManager.openconnect' was not installed.
>>
>> I read the manual which says:
>>
>> ‘vpn-plugins’ (default: ‘'()’)
>> This is the list of available plugins for virtual private
>> networks (VPNs). An example of this is the
>> ‘network-manager-openvpn’ package, which allows NetworkManager
>> to manage VPNs via OpenVPN.
>>
>> I therefore tried this in my config
>>
>> (network-manager-service-type
>> config => (network-manager-configuration
>> (inherit config)
>> (dns "dnsmasq")
>> (vpn-plugins '("network-manager-openconnect"))
>> ))
>
> If nothing else, you should go with the `network-manager-openconnect'
> package object here. In your snippet, you are referring to the string
> "network-manager-openconnect" instead.
>
> Something like the following should solve your immediate issue:
> (vpn-plugins (list network-manager-openconnect))
Makes total sense and fixed my issue. lol. Thank you!
>> This email is subject to a disclaimer.
>>
>> Visit the FNB website and view the email disclaimer by clicking the "About FNB + Legal" and "Legal Matters" links.
>> If you are unable to access our website, please contact us to send you a copy of the email disclaimer.
> You might want to reconsider adding this disclaimer, as this is a
> mailing list with publicly available archive at
> https://secure-web.cisco.com/1ZqvkATgEJFvkJ0wXj8_z-wGnZxvhwLIU37BHOD45mu8BrI5hPANkSnMovtDIesYvFhfwcMF9SB3LrdwGv93tSbkjtod_wj4NEdkVwwobbtbyHtHDuSZmzbnjuguSGq3xrsU_kSNmXaJl44RuAvnuqUGgit_azcAyomzTSbRzxxPvsZrevJ1kJyhakR0ZmLg9Y9-4lDg3KCILV3yD_PNoNNdlRyr9a4zGkQs1-2oWt6O4N0dskups5ky9TWpAX22wKjkcV6lkhkMPOmMi3E8VyDcL73U6--0xfUNoANQas0ab0nBJMe46uj4kPbYxL5xyes5MYR0tfu0uQ3-wt9Gf1g/https%3A%2F%2Flists.gnu.org%2Farchive%2Fhtml%2Fhelp-guix%2F
My personal mail server was down due to upstream ISP blocking incoming
port 80 (go figure!), which broke my SSL cert renewals, so I temporarily
used work mail. :grin:
next prev parent reply other threads:[~2019-09-09 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 20:34 network-manager-openconnect setup Santana, Divan
2019-08-10 21:08 ` Jelle Licht
2019-09-09 20:01 ` divan [this message]
2019-08-11 19:24 ` Mark H Weaver
2019-09-09 20:02 ` network-manager-openconnect setup - [External Email] divan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rwpqlwv.fsf@fnb.co.za \
--to=divan@santanas.co.za \
--cc=help-guix@gnu.org \
--cc=jlicht@fsfe.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).