New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
windows client and proxy SOCKS: DeviceIoControl(OVPN_IOCTL_START_VPN) failed: Invalid descriptor(errno=6) #522
Comments
Mmmmh. This is interesting. First of all, the problem is that the default driver is now Using wintun (or So, the actual bug here is "if using win-dco, refuse socks proxy setting or turn off dco automatically". It works if the
... and it seems we do not detect this case correctly. |
If this is from the GUI, may be we could automatically add --disable-dco to the command line when proxy is set via the GUI? This wont be enough in general, but could help. |
Sending OTOH, is there anything besides proxy setting (which are all not DCO compatible) which can be set in the GUI? |
Apart from This is the fist time we find one of those options could cause a conflict. |
I think the only problematic one here is So maybe if proxies are involved make it always send @lstipakov what would you recommend? |
On further thought, the same could be achieved more generally by disabling dco in the core when |
Makes sense to me. Can you send a patch or would you prefer someone else take care of it? |
But then I found this (in 2.6.1 onwards)
And indeed the error log has:
It seems
This is called from init() without any checks for |
I presume this comes from the fact that the logic in windows is not boolean (DCO on / off), but we have this windows_driver attribute leading the way. @lstipakov maybe on windows, next to disabling the DCO flag we should turn windows_driver to something else? |
Just reproduced the problem. Looking into it. |
Not sure how I tested that commit on Windows - it is a bit too late at that point to disable DCO at least on Windows since we've already done certain DCO-specific adjustments like |
Commit 45a1cb2 ("Disable DCO if proxy is set via management") attempted to disable DCO when proxy is set via management interface. However, at least on Windows this doesn't work, since: - setting tuntap_options->disable_dco to true is not enough to disable DCO - at this point it is a bit too late, since we've already done DCO-specific adjustments Since proxy could be set via management only if --management-query-proxy is specified, the better way would be to add a check to dco_check_startup_option(). Github: fixes OpenVPN#522 Change-Id: I16d6a9fefa317d7d4a195e786618328445bdbca8 Signed-off-by: Lev Stipakov <lev@openvpn.net>
Commit 45a1cb2 ("Disable DCO if proxy is set via management") attempted to disable DCO when proxy is set via management interface. However, at least on Windows this doesn't work, since: - setting tuntap_options->disable_dco to true is not enough to disable DCO - at this point it is a bit too late, since we've already done DCO-specific adjustments Since proxy can be set via management only if --management-query-proxy is specified, the better way is to add a check to dco_check_startup_option(). Github: fixes #522 Change-Id: I16d6a9fefa317d7d4a195e786618328445bdbca8 Signed-off-by: Lev Stipakov <lev@openvpn.net> Acked-by: Frank Lichtenheld <frank@lichtenheld.com> Message-Id: <20240318181744.20625-1-gert@greenie.muc.de> URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg28415.html Signed-off-by: Gert Doering <gert@greenie.muc.de> (cherry picked from commit fd6b839)
Describe the bug
There is no connection via proxy. Error in the log. Exiting due to fatal error.
To Reproduce
using a proxy SOCKS setting without an option windows-driver wintun,
ERROR:
Expected behavior
connection via proxy SOCKS without error and without modification of settings
Version information (please complete the following information):
Additional context
use config:
logs:
2-6-6-err.txt
2-6-9-err.txt
if you add the option windows-driver wintun connection is ok, there are no errors
log:
2-6-9-drv-wintun-connect-OK.txt
The text was updated successfully, but these errors were encountered: