The option doesn't exist anymore so don't point
people to it.
But add it to the list of unsupported options.
Change-Id: I78c6f335c635e97bb41d26ed8908a978d7b49387
Signed-off-by: Frank Lichtenheld <frank@lichtenheld.com>
Acked-by: Gert Doering <gert@greenie.muc.de>
Gerrit URL: https://gerrit.openvpn.net/c/openvpn/+/1426
Message-Id: <
20251210074904.27067-1-gert@greenie.muc.de>
URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg34970.html
Signed-off-by: Gert Doering <gert@greenie.muc.de>
--opt-verify
Removed in OpenVPN 2.7. This option does not make sense anymore as option
strings may not match due to the introduction of parameters negotiation.
+
+--windows-driver
+ Removed in OpenVPN 2.7. OpenVPN will always use ovpn-dco as the default
+ driver on Windows. It will fall back to tap-windows6 if options are used
+ that are incompatible with ovpn-dco.
On Windows, only the names :code:`tun` and :code:`tap` are supported.
Selection among multiple installed drivers or driver instances is done
- with ``--dev-node`` and ``--windows-driver``.
+ with ``--dev-node``.
--dev-node node
This is a highly system dependent option to influence tun/tap driver
}
else
{
- if (o->windows_driver == DRIVER_DCO)
- {
- msg(M_WARN,
- "Option --windows-driver ovpn-dco is ignored because Data Channel Offload is disabled");
- o->windows_driver = WINDOWS_DRIVER_TAP_WINDOWS6;
- }
- else if (o->windows_driver == WINDOWS_DRIVER_UNSPECIFIED)
- {
- o->windows_driver = WINDOWS_DRIVER_TAP_WINDOWS6;
- }
+ o->windows_driver = WINDOWS_DRIVER_TAP_WINDOWS6;
}
#else /* _WIN32 */
if (dco_enabled(o) && o->dev_node)
if (tt->backend_driver != windows_driver)
{
msg(M_FATAL,
- "Adapter '%s' is using %s driver, %s expected. If you want to use this device, adjust --windows-driver.",
+ "Adapter '%s' is using %s driver, %s expected.",
dev_node, print_tun_backend_driver(windows_driver),
print_tun_backend_driver(tt->backend_driver));
}