Opened 19 months ago
Closed 17 months ago
#1480 closed Bug / Defect (fixed)
dco-win adapter stays in connected state after tunnel disconnect
Reported by: | kitsune-one | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Generic / unclassified | Version: | OpenVPN git master branch (Community Ed) |
Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
Cc: |
Description
Using OpenVPN 2.6_git [git:master/6bbd89c5c82e7a23] Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] [DCO] built on Oct 11 2022
netsh int show int before connecting shows these adapters and their states
Admin State State Type Interface Name ------------------------------------------------------------------------- Enabled Connected Dedicated Wi-Fi Enabled Disconnected Dedicated OpenVPN TAP-Windows6 Enabled Disconnected Dedicated Wintun2 Enabled Disconnected Dedicated OpenVPN Data Channel Offload
After a successfully starting a tunnel using --windows-driver ovpn-dco
and then disconnecting it (the GUI was used to start and stop).
Admin State State Type Interface Name ------------------------------------------------------------------------- Enabled Connected Dedicated Wi-Fi Enabled Disconnected Dedicated OpenVPN TAP-Windows6 Enabled Disconnected Dedicated Wintun2 Enabled Connected Dedicated OpenVPN Data Channel Offload
Expected: the dco adapter should go back to state "disconnected" after the tunnel is shut down. A manual disable/enable cycle fixes this.
Change History (3)
Note: See
TracTickets for help on using
tickets.
This should be fixed in 0.8.2 version of dco-win driver.
You can check the version of the driver with this PowerShell? snippet (requires elevation):
"Works on my machine".
After connection:
After disconnect:
Can you retest with the latest installer from here?