-
Notifications
You must be signed in to change notification settings - Fork 397
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
No adapter domain suffix with DCO driver on Windows (in ovpnagent mode) #304
Comments
I've prepared the fix, currently |
lstipakov
pushed a commit
to lstipakov/openvpn3
that referenced
this issue
Apr 5, 2024
Setting ADAPTER_DOMAIN_SUFFIX for non-DHCP adapters requires registry modification. For that, we need adapter GUID. This passes adapter GUID from agent to client via /tun-open call and then from client to agent via /tun-setup call, when adapter domain suffix is set. Github: OpenVPN#304 Signed-off-by: Lev Stipakov <lev@openvpn.net> Signed-off-by: Krasovskiy Saveliy Igorevich <skrasovskiy@ozon.ru>
flichtenheld
pushed a commit
to flichtenheld/openvpn3
that referenced
this issue
Apr 25, 2024
Setting ADAPTER_DOMAIN_SUFFIX for non-DHCP adapters requires registry modification. For that, we need adapter GUID. This passes adapter GUID from agent to client via /tun-open call and then from client to agent via /tun-setup call, when adapter domain suffix is set. Github: OpenVPN#304 Signed-off-by: Lev Stipakov <lev@openvpn.net> Signed-off-by: Krasovskiy Saveliy Igorevich <skrasovskiy@ozon.ru>
Fixed in 3.9. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I came from this issue: OpenVPN/openvpn#306, but it seems like OpenVPN3 should support it. However after debugging it a bit I saw this, log from DCO agent:
Log from Wintun:
As you can see, Wintun properly logs not only suffix, but also interface GUID.
But it should be logged if everything would be okay:
Because tap_guid variable is empty for some reason, the code which manipulates the registry:
Writes in a complitely wrong place, in the
SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces
root, and I clearly see it:It's definitely a bug, currently trying to debug the reason behind this behavior.
The text was updated successfully, but these errors were encountered: