unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: 39542@debbugs.gnu.org, damien@cassou.me
Subject: bug#39542: Adding openvpn client configurations to guix system
Date: Mon, 10 Feb 2020 07:31:21 -0500	[thread overview]
Message-ID: <1BD29F0F-1268-4526-828D-C2AC25CFE2E5@lepiller.eu> (raw)
In-Reply-To: <87blq63hyj.fsf@cassou.me>

Le 10 février 2020 04:33:08 GMT-05:00, Damien Cassou <damien@cassou.me> a écrit :
>Hi,
>
>both OpenVPN and NetworkManager read network configurations from
>/etc. This should make it possible to configure your favorite VPN
>client
>configurations (and maybe wifi access points) in your /etc/config.scm.
>
>An OpenVPN client connection typically consists of *.key files, *.pem
>files and *.crt files. These should be placed under
>/etc/openvpn/client/.
>
>Each OpenVPN client connection must be declared at the Network manager
>level too. This means adding a *.nmconnection file in
>/etc/NetworkManager/system-connections/.
>
>It would be great if Guix could make that possible from my
>/etc/config.scm file.
>
>Thank you for your great work!

Hi,

We already have an openvpn-client-service-type and an openvpn-server-service-type. It's not linked to network manager though, I have no idea what it expects there. What do you need exactly?

https://guix.gnu.org/manual/devel/en/html_node/VPN-Services.html#VPN-Services

  reply	other threads:[~2020-02-10 12:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10  9:33 bug#39542: Adding openvpn client configurations to guix system Damien Cassou
2020-02-10 12:31 ` Julien Lepiller [this message]
2020-02-10 15:57   ` Damien Cassou
2020-08-01 13:44     ` david larsson
2020-08-01 14:58       ` david larsson
2020-08-02 18:33       ` Damien Cassou
2022-03-15 15:10         ` 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

  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=1BD29F0F-1268-4526-828D-C2AC25CFE2E5@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=39542@debbugs.gnu.org \
    --cc=damien@cassou.me \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).