From: ludo@gnu.org (Ludovic Courtès)
To: Benjamin Slade <beoram@gmail.com>
Cc: Guix-Help <help-guix@gnu.org>
Subject: Re: openvpn with networkmanager
Date: Sun, 09 Sep 2018 12:25:02 +0200 [thread overview]
Message-ID: <871sa3dl35.fsf@gnu.org> (raw)
In-Reply-To: <8736up6w7l.fsf@jnanam.net> (Benjamin Slade's message of "Tue, 04 Sep 2018 10:53:02 -0600")
Hi Benjamin,
Benjamin Slade <beoram@gmail.com> skribis:
> I have the following definition in my config.scm, which I call in
> defining the operating system:
>
> ````
> (define %slade-desktop-services
> (modify-services %desktop-services
> (network-manager-service-type config =>
> (network-manager-configuration
> (inherit config)
> (vpn-plugins (list network-manager-openvpn))))))
> ````
>
> This does indeed enable the OpenVPN module of NetworkManager, but
> NetworkManager doesn't automatically read in the *.opvn files in
> /etc/openvpn (which is probably expected), but moreover as an ordinary
> user I'm not allowed to create them. Is the best thing to login as root
> and add these to NetworkManager?
IIRC, NM has a tool to import OpenVPN config files, though it only
understands a subset of the syntax; you have to run it as root:
sudo nmcli connection import type openvpn file /path/to/whatever.ovpn
Then I think something was broken with VPN support in NM, though I
forgot the details…
HTH,
Ludo’.
next prev parent reply other threads:[~2018-09-09 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 16:53 openvpn with networkmanager Benjamin Slade
2018-09-09 10:25 ` Ludovic Courtès [this message]
2018-09-10 4:27 ` Benjamin Slade
2018-09-10 16:05 ` Adam Massmann
2018-09-11 1:45 ` Benjamin Slade
2018-09-11 8:28 ` Julien Lepiller
2018-09-11 16:50 ` Adam Massmann
2018-09-11 17:53 ` Benjamin Slade
2018-09-13 8:54 ` Ludovic Courtès
2018-09-18 3:55 ` Benjamin Slade
2018-11-09 6:39 ` swedebugia
2019-01-08 20:48 ` Maxim Cournoyer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871sa3dl35.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beoram@gmail.com \
--cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.