]> www.infradead.org Git - users/dwmw2/openconnect.git/commit
Don't set Legacy IP address on Windows tunnel interface within OpenConnect itself
authorDaniel Lenski <dlenski@gmail.com>
Thu, 1 Apr 2021 00:21:41 +0000 (17:21 -0700)
committerDaniel Lenski <dlenski@gmail.com>
Fri, 10 Sep 2021 18:27:34 +0000 (11:27 -0700)
commita2c4d2f5e73370fff18f0013a96c2f9a5005b3a2
treeaedf39836ae117500b040696a7160e8611c0e394
parentba8e9e8bbf851e38ff230551dacbf149fe551e27
Don't set Legacy IP address on Windows tunnel interface within OpenConnect itself

The pre-existing Windows routing connection script (vpnc-script-win.js) was
not able to reliably set the Legacy IP address of the tunnel interface, so
we've been setting it in OpenConnect itself since
60d1f092e35f05217f1c96823c4f1b86c7915bbd.

As of https://gitlab.com/openconnect/vpnc-scripts/-/merge_requests/26, we've
got vpnc-script-win.js setting the Legacy IP address correctly, and IPv6 as
well. We should leave this as the script's responsibility for
cross-platform consistency.

Signed-off-by: Daniel Lenski <dlenski@gmail.com>
wintun.c