unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Divan Santana <divan@santanas.co.za>
Cc: 37369@debbugs.gnu.org, help-guix@gnu.org
Subject: bug#37369: Getting network-manager-openconnect to work
Date: Sat, 28 Sep 2019 17:34:43 +0200	[thread overview]
Message-ID: <20190928153443.r4kbd3tninivufq6__25866.7558476859$1569684921$gmane$org@pelzflorian.localdomain> (raw)
In-Reply-To: <87ftkgtsjb.fsf@santanas.co.za>

For me, before editing the connection, NetworkManager crashed with a
segfault and restarted after attempting to connect with a faulty VPN
connection.  The same may be what happens to you.

However, I can add a new connection with gnome-control-center or
nm-connection-editor (without using any “connection file”; GNOME asks
me for the sudo password though) and then I fill in the gateway field.
I can then use for example nmtui to activate the connection.

I noticed I have openconnect in my config.scm’s system packages, but I
believe it is not relevant.

I use:

(network-manager-service-type config =>
  (network-manager-configuration
    (inherit config)
    (dns "dnsmasq")
    (vpn-plugins (list network-manager-openconnect))))

dnsmasq is probably not required, but I do not know.

Regards,
Florian

  parent reply	other threads:[~2019-09-28 15:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87sgp4pj7s.fsf@santanas.co.za>
2019-09-10 11:21 ` Getting network-manager-openconnect to work pelzflorian (Florian Pelz)
2019-09-11  7:38   ` bug#37369: " Efraim Flashner
     [not found]   ` <20190911073822.GI977@E5400>
2019-09-11 11:39     ` pelzflorian (Florian Pelz)
2019-09-11 20:46   ` Ludovic Courtès
2019-09-12  5:34     ` pelzflorian (Florian Pelz)
2019-09-16 15:57       ` Ludovic Courtès
2019-09-16 16:06         ` pelzflorian (Florian Pelz)
2019-09-27 16:37           ` bug#37369: " pelzflorian (Florian Pelz)
2019-09-28 14:00             ` Divan Santana
2019-09-28 14:16             ` Divan Santana
     [not found]             ` <87ftkgtsjb.fsf@santanas.co.za>
2019-09-28 15:34               ` pelzflorian (Florian Pelz) [this message]
2019-09-28 16:47               ` pelzflorian (Florian Pelz)
     [not found]               ` <20190928153443.r4kbd3tninivufq6@pelzflorian.localdomain>
2019-09-29  7:54                 ` pelzflorian (Florian Pelz)
     [not found]               ` <20190928164704.vtky5rof6wtlu5cu@pelzflorian.localdomain>
2019-10-03 11:51                 ` Divan Santana
2019-09-16 11:53   ` pelzflorian (Florian Pelz)
2020-04-12 19:46   ` divan
2020-05-04 19:43   ` bug#37369: (no subject) Divan Santana via web

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='20190928153443.r4kbd3tninivufq6__25866.7558476859$1569684921$gmane$org@pelzflorian.localdomain' \
    --to=pelzflorian@pelzflorian.de \
    --cc=37369@debbugs.gnu.org \
    --cc=divan@santanas.co.za \
    --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 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).