pulse.xml 2.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  1. <PAGE>
  2. <INCLUDE file="inc/header.tmpl" />
  3. <VAR match="VAR_SEL_PROTOCOLS" replace="selected" />
  4. <VAR match="VAR_SEL_PULSE" replace="selected" />
  5. <PARSE file="menu1.xml" />
  6. <PARSE file="menu2-protocols.xml" />
  7. <INCLUDE file="inc/content.tmpl" />
  8. <h1>Pulse Connect Secure</h1>
  9. <p>Support for Pulse Connect Secure was added to OpenConnect in June 2019,
  10. for the 8.04 release. In most cases it supersedes the older Juniper Network
  11. Connect support. It is a much saner protocol.</p>
  12. <p>Pulse mode is requested by adding <tt>--protocol=pulse</tt>
  13. to the command line:
  14. <pre>
  15. openconnect --protocol=pulse vpn.example.com
  16. </pre></p>
  17. <p>The TCP transport for Pulse Connect Secure works over
  18. <a href="https://trustedcomputinggroup.org/resource/tnc-if-t-binding-to-tls/">IF-T/TLS</a>,
  19. first using EAP (and EAP-TTLS if certificates are being used) for
  20. authentication and then passing traffic over IF-T messages over
  21. the same transport. Just as with the older Juniper protocol, the UDP
  22. transport is <a href="https://tools.ietf.org/html/rfc3948">ESP</a>.</p>
  23. <h2>Authentication</h2>
  24. <p>The authentication cookies are compatible with the
  25. <a href="juniper.html">Juniper</a> mode, which means that external
  26. tools like <a href="https://github.com/russdill/juniper-vpn-py">juniper-vpn-py</a>
  27. should be usable with OpenConnect in Pulse mode too.</p>
  28. <h3>Host Checker</h3>
  29. <p>Support for Host Checker, also known as TNCC, has not yet been investigated and
  30. implemented for Pulse mode. The Juniper support may suffice for some users.</p>
  31. <h2>Connectivity</h2>
  32. <p>Once authentication is complete, the VPN connection can be
  33. established. Both Legacy IP and IPv6 should be working. However, some
  34. Pulse VPNs will not provide full IPv6 connectivity unless a recent
  35. version of the official Pulse client for Windows is spoofed (see
  36. <a href="https://gitlab.com/openconnect/openconnect/-/issues/254#note_661398964">comment
  37. on GitLab issue #254</a>. For example:</p>
  38. <pre>
  39. ./openconnect --protocol=pulse --useragent "Pulse-Secure/9.1.11.6725" --os=win
  40. </pre>
  41. <INCLUDE file="inc/footer.tmpl" />
  42. </PAGE>