We are now working on adding Juniper support to OpenConnect. Eric, or
indeed anyone else, if you're interested in testing please send an email
either to the openconnect-devel mailing list or to me directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Fri, 2014-02-14 at 04:42 +, Eric Gillingham wrote:
Failed to read from SSL socket: A TLS packet with unexpected length
was received.
I see a different error on that server:
Failed to read from SSL socket: The TLS connection was non-properly
terminated.
For me it's fixed by
On Fri, 2014-02-14 at 12:54 +, dwmw2 wrote:
It just seems to be giving web pages back. And in fact the AnyConnect
client seems to have the same issue. (Although I tested with an
ancient 2.2.0136 since my newer version started segfaulting and
dying.)
Turns out 3.1.03103 stops segfaulting
According to https://dir.jpl.nasa.gov/tfa/TFA_RAS_instructions.pdf this
is a Juniper VPN, not Cisco AnyConnect. I'm not going to lose sleep over
the fact that we can't connect to it!
Supporting the Juniper VPN might not actually be that hard, if it's at
all similar to AnyConnect. And it's likely
Good catch, thanks for helping look into this failure. OpenConnect does
not connect to all VPNs, only Cisco AnyConnect VPNs. The specific VPN
you are trying to use is not an AnyConnect VPN, so OpenConnect is not
expected to work with it. Closing this bug report as invalid.
** Changed in:
That version isn't in the saucy repository, I manually downloaded and
installed https://launchpad.net/ubuntu/trusty/amd64/openconnect/5.02-1
and https://launchpad.net/ubuntu/trusty/amd64/libopenconnect2/5.02-1
openconnect vpn...
POST https://vpn...
Attempting to connect to server ...:443
SSL
** Changed in: openconnect (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1225276
Title:
cannot connect to some gateways
To manage notifications about this
This behavior sounds exactly like that reported in bug #1229195. Can you
update to openconnect 5.02-1 that was just uploaded yesterday and see if
this version fixes the problem for you without the need for the --no-
xmlpost option?
--
You received this bug notification because you are a member
Yes:
openconnect --no-xmlpost vpn...
GET https://vpn.jpl.nasa.gov/
Attempting to connect to server ...:443
SSL negotiation with vpn...
Server certificate verify failed: signer not found
Certificate from VPN server vpn failed verification.
Reason: signer not found
Enter 'yes' to accept, 'no'
Hi, still waiting for a response to my last question in comment #1:
Does the connection succeed when the --no-xmlpost option is given to
openconnect?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, thanks for your bug report. You say you are seeing the same bug as
the linked bug report, but that bug was fixed with version 5.01 of
openconnect.
Can you confirm that you are running version 5.01 of openconnect when
this failure occurs (openconnect --version)?
Does the connection succeed
openconnect --version
OpenConnect version v5.01
Using GnuTLS. Features present: PKCS#11, TOTP software token, DTLS (using
OpenSSL)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1225276
Title:
As mentioned in the bug report, I am running 5.01:
Installed openconnect versions, this is on saucy:
ii libopenconnect2:amd64 5.01-1 amd64
ii openconnect 5.01-1 amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
13 matches
Mail list logo