From 001fdabcce6aec01d7abdd69e24bd6a07cbb0975 Mon Sep 17 00:00:00 2001
From: Daniel Lenski <dlenski@gmail.com>
Date: Thu, 26 Aug 2021 12:43:54 -0700
Subject: [PATCH] Mention that some Pulse VPNs need to spoof official UA/OS to
 make IPv6 work

As discussed in https://gitlab.com/openconnect/openconnect/-/issues/254#note_661398964

Signed-off-by: Daniel Lenski <dlenski@gmail.com>
---
 www/pulse.xml | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/www/pulse.xml b/www/pulse.xml
index 64ee29f8..e7bd515f 100644
--- a/www/pulse.xml
+++ b/www/pulse.xml
@@ -42,7 +42,15 @@ implemented for Pulse mode. The Juniper support may suffice for some users.</p>
 <h2>Connectivity</h2>
 
 <p>Once authentication is complete, the VPN connection can be
-established. Both Legacy IP and IPv6 should be working.</p>
+established. Both Legacy IP and IPv6 should be working. However, some
+Pulse VPNs will not provide full IPv6 connectivity unless a recent
+version of the official Pulse client for Windows is spoofed (see
+<a href="https://gitlab.com/openconnect/openconnect/-/issues/254#note_661398964">comment
+on GitLab issue #254</a>. For example:</p>
+
+<pre>
+  ./openconnect --protocol=pulse --useragent "Pulse-Secure/9.1.11.6725" --os=win
+</pre>
 
 	<INCLUDE file="inc/footer.tmpl" />
 </PAGE>
-- 
2.50.1