v8.04: Connection works with --juniper flag; error if --protocol=pulse is used

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

With v8.04, I am unable to connect to my VPN if I use the
--protocol=pulse option. I am still able to connect by using the
--juniper option.

Here is the output (x's mine):
Connected to xxx.xxx.xxx.xxx:443
SSL negotiation with xxx.xxx.xxx.xxx
Connected to HTTPS on xxx.xxx.xxx.xxx
Got HTTP response: HTTP/1.1 101 Switching Protocols
Unhandled Pulse authentication packet, or authentication failure
E 0000:  01 03 00 28 fe 00 0a 4c  00 00 00 01 00 00 00 4f 
|...(...L.......O|
E 0010:  40 00 00 1a 01 01 00 12  fe 00 0a 4c 00 00 00 05 
|@..........L....|
E 0020:  01 00 8b 21 5f 5d 05 83                           |...!_]..|
Failed to obtain WebVPN cookie

The above output was the same for both commands below:
sudo openconnect --protocol=pulse xxx.xxx.xxx.xxx
--authgroup="Dual-Factor Pulse Clients" --useragent nvsvc --user xxxxxx
sudo openconnect --protocol=pulse xxx.xxx.xxx.xxx --user xxxxxx

The VPN works with the official Pulse Secure client, so I think that's
the right protocol, but maybe they're actually running with something
that only works with the nc protocol and not pulse?

Has anyone seen this before, or have any tips on what to try next?

Thank you,
Will

Attachment: pEpkey.asc
Description: application/pgp-keys

_______________________________________________
openconnect-devel mailing list
openconnect-devel@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/openconnect-devel

[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux