GNU bug report logs - #37369
Getting network-manager-openconnect to work

Previous Next

Package: guix;

Reported by: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>

Date: Tue, 10 Sep 2019 11:22:02 UTC

Severity: normal

Full log


Message #38 received at 37369 <at> debbugs.gnu.org (full text, mbox):

From: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
To: Divan Santana <divan <at> santanas.co.za>
Cc: 37369 <at> debbugs.gnu.org, Ludovic Courtès <ludo <at> gnu.org>,
 help-guix <at> gnu.org
Subject: Re: bug#37369: Getting network-manager-openconnect to work
Date: Sat, 28 Sep 2019 17:34:43 +0200
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




This bug report was last modified 5 years and 39 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.