Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#45645 - [openconnect] connection error

Attached to Project: Arch Linux
Opened by John (hlistalin) - Tuesday, 14 July 2015, 15:29 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 15 July 2015, 03:21 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Ionut Biru (wonder)
Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:
when attempting to connect to the server via openconnect
Attempting to connect to server [Server]
SSL negotiation with [Server]
SSL connection failure: A TLS fatal alert has been received.
Failed to open HTTPS connection to [Server]
Failed to obtain WebVPN cookie


Additional info:
* openconnect 1:7.06-2

Steps to reproduce:
connect to server with tls
This task depends upon

Comment by Felix Yan (felixonmars) - Wednesday, 15 July 2015, 05:55 GMT
Cannot reproduce here. Please double check your client/server configuration
Comment by John (hlistalin) - Wednesday, 15 July 2015, 08:56 GMT

In the previous version of such an error is not repeated. connection is established by different protocols TLS?
Comment by Felix Yan (felixonmars) - Wednesday, 15 July 2015, 10:14 GMT
Which previous version?

My connection works just fine:
Established DTLS connection (using GnuTLS). Ciphersuite (DTLS1.2)-(RSA)-(AES-128-GCM).
Comment by John (hlistalin) - Wednesday, 15 July 2015, 12:02 GMT
with v. 6.00-3 connect fine
Comment by Felix Yan (felixonmars) - Wednesday, 15 July 2015, 16:33 GMT
I would suggest to report to upstream with more details, since I don't think it's a packaging problem.
Comment by Tianjiao Yin (ytj) - Sunday, 20 March 2016, 07:32 GMT
Actually I feel it is a packaging problem. I fixed a similar issue by installing networkmanager-openconnect

Here is the list of installed packages from my terminal log:

Packages (14) gpm-1.20.7-6 jansson-2.7-1 libmm-glib-1.4.12-1 libndp-1.5-1 libnewt-0.52.18-3 libnm-glib-1.0.10-2 libpgm-5.2.122-2 libsecret-0.18.4-1 libsodium-1.0.8-1 libteam-1.23-1 networkmanager-1.0.10-2 slang-2.3.0-1 zeromq-4.1.4-1 networkmanager-openconnect-1.0.8-1


Though I am not sure which package fixed this.
Comment by Levente Polyak (anthraxx) - Tuesday, 12 February 2019, 01:22 GMT
whats the state with vpnc 1:0.5.3.r452.r67-1 and openconnect 1:8.02-1?
Comment by Krisztian Fekete (e3) - Tuesday, 12 February 2019, 08:58 GMT
@anthraxx I have just run into this problem after a pacman -Syu :

DTLS handshake failed: A TLS fatal alert has been received.

After removing openconnect (pacman -Rs openconnect, though this removal step was probably unneeded), and installing networkmanager-openconnect the problem disappeared (thanks @ytj!).

I am not using networkmanager, it was not installed before, have not thought using that package.

These were the newly installed
Packages (5) libnm-1.14.5dev+17+gba83251bb-2 openconnect-1:8.02-1 pcsclite-1.8.24-1 vpnc-1:0.5.3.r454.r67-1
networkmanager-openconnect-1.2.5dev+110+g524a2e0-2

Comment by Levente Polyak (anthraxx) - Tuesday, 12 February 2019, 16:13 GMT
You are aware that networkmanager-openconnect pulls in openconnect so removing did literally nothing?
Anyway, now not an issue with openconnect anymore if that worked

Loading...