From: Maxime Devos <maximedevos@telenet.be>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>, 54398@debbugs.gnu.org
Subject: bug#54398: Adding network-manager-openvpn requires a full reboot
Date: Tue, 15 Mar 2022 17:32:01 +0100 [thread overview]
Message-ID: <146ed7e23e6473d2e00ad7c0cea7f5fc43843051.camel@telenet.be> (raw)
In-Reply-To: <87sfrjck7w.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
Maxim Cournoyer schreef op di 15-03-2022 om 11:24 [-0400]:
> 1. Add the 'network-manager-openvpn' plugin to your
> 'network-manager-configuration', like so:
>
> --8<---------------cut here---------------start------------->8---
> (modify-services %desktop-services
> [...]
> (network-manager-service-type config =>
> (network-manager-configuration
> (inherit config)
> (vpn-plugins (list network-manager-openvpn))))
> --8<---------------cut here---------------end--------------->8---
Looking at 'network-manager-environment'
(define network-manager-environment
(match-lambda
(($ <network-manager-configuration> network-manager dns vpn-
plugins)
;; Define this variable in the global environment such that
;; "nmcli connection import type openvpn file foo.ovpn" works.
`(("NM_VPN_PLUGIN_DIR"
. ,(file-append (vpn-plugin-directory vpn-plugins)
"/lib/NetworkManager/VPN")))))),
I expect a potential issue to be that NM_VPN_PLUGIN_DIR is a
/gnu/store/... file name and hence the plugins in there are
not adjusted by a reconfiguration. Maybe it could instead
refer to somewhere in /run/current-system/...?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-03-15 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 15:24 bug#54398: Adding network-manager-openvpn requires a full reboot Maxim Cournoyer
2022-03-15 16:32 ` Maxime Devos [this message]
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=146ed7e23e6473d2e00ad7c0cea7f5fc43843051.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54398@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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.