This thread appears to be describing THREE SEPARATE PROBLEMS, which likely have nothing to do with Ubuntu's packaging specifically. Please submit bug reports at https://gitlab.com/openconnect/openconnect/-/issues.
@Ingo Karkat:
> What helped for me was switching from
>
> $ sudo openconnect --protocol=pulse ...
>
> to
>
> $ sudo openconnect --juniper ...
>
> Which is odd, because my company's VPN is Pulse Secure?!
All Pulse Secure VPNs are backwards-compatible with the Juniper protocol. The two protocols are completely different, and both are *terrible* messes… but our understanding of the Juniper protocol is more complete.
If you want to improve the Pulse protocol support, please contribute over at Gitlab.
I'm one of the OpenConnect developers.
This thread appears to be describing THREE SEPARATE PROBLEMS, which likely have nothing to do with Ubuntu's packaging specifically. Please submit bug reports at https:/ /gitlab. com/openconnect /openconnect/ -/issues.
@Ingo Karkat:
> What helped for me was switching from
>
> $ sudo openconnect --protocol=pulse ...
>
> to
>
> $ sudo openconnect --juniper ...
>
> Which is odd, because my company's VPN is Pulse Secure?!
All Pulse Secure VPNs are backwards- compatible with the Juniper protocol. The two protocols are completely different, and both are *terrible* messes… but our understanding of the Juniper protocol is more complete.
If you want to improve the Pulse protocol support, please contribute over at Gitlab.
Read https:/ /www.infradead. org/openconnect /juniper. html for a bit more explanation.