DCO-Win: explicit-exit-notify is dropped when using DC
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- networking
Research direction
Start by tracing the log message “Attempting to send data packet while data channel offload is in use” and how the client negotiates cc-exit when using DCO-Win. Compare that path with the reported TAP-Windows6 behavior and the documented fallback for explicit-exit-notify. Done means establishing whether DCO-Win should deliver the notification when cc-exit is unavailable and, if so, identifying how that delivery can work.
Written by the indexing model from the issue text.
Description
DCO-Win: explicit-exit-notify is not delivered when DCO is used
I found a reproducible interoperability problem with explicit-exit-notify when using the Windows DCO driver.
This is not specific to Wintun, and it is not specific to one particular OpenVPN GUI version.
The problem is reproducible whenever DCO is used, while TAP-based connections correctly notify the server about the disconnect.
Server:
- MikroTik RouterOS 7.24.4
- OpenVPN server
- UDP
Client:
- Windows
- OpenVPN 2.7.x
- UDP
- explicit-exit-notify 1
Observed behavior
With a TAP-Windows6 connection, disconnecting the client immediately removes the OVPN session from the MikroTik server.
With DCO-Win, the client disconnects locally, but the OVPN session remains on the MikroTik server until the server-side keepalive timeout expires.
The same behavior is reproducible with different OpenVPN GUI/OpenVPN client versions when DCO is used.
This should also be considered in the context of the fact that Wintun is no longer supported in OpenVPN 2.7. I am therefore using TAP-Windows6 as the non-DCO comparison, rather than relying on Wintun.
Relevant OpenVPN 2.7.7 log
With DCO enabled:
text
2026-10-06 16:39:53 Timers: ping 15, ping-restart 45, inactive 20
2026-10-06 16:39:53 Protocol options: explicit-exit-notify 1
2026-10-06 16:40:16 SIGTERM received, sending exit notification to peer
2026-10-06 16:40:16 Attempting to send data packet while data channel offload is in use. Dropping packet4
The client therefore detects the disconnect and attempts to send the exit notification, but the packet is dropped because DCO is in use.
The negotiated protocol options also do not contain cc-exit:
text
Protocol options: explicit-exit-notify 1
There is no:
text
protocol-flags cc-exit
According to the OpenVPN 2.7 documentation, if both peers support sending the exit notification over the control channel, it is sent that way. Otherwise it is sent as a data-channel message, which is ignored when data-channel offload is being used.
My MikroTik server does not appear to negotiate cc-exit with the DCO client.
Important comparison
The same MikroTik server and the same:
text
explicit-exit-notify 1
behave correctly when using TAP-Windows6:
TAP-Windows6:
- client disconnect
- exit notification reaches the server
- OVPN session is removed immediately
DCO-Win:
- client disconnect
- OpenVPN attempts to send exit notification
- DCO drops the packet
- server does not immediately remove the session
- session remains until keepalive timeout
So the relevant difference appears to be DCO vs. non-DCO, rather than Wintun vs. DCO or one particular OpenVPN GUI release.
Question
What is the expected behavior of DCO-Win when connecting to an OpenVPN server which supports explicit-exit-notify but does not negotiate cc-exit?
Is there currently a supported way for DCO-Win to deliver explicit-exit-notify in this situation?
Or is this an expected DCO interoperability limitation which should be addressed so that the client can still notify the peer when cc-exit is unavailable?
Thanks!
- Dominant language
- C
- Stars
- 14.8k
- Forks
- 3.4k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenVPN/openvpn
-
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
-
CVE-2026-11604 vs OpenVPN 2.7.x DocumentationMay be free again @lstipakov claimed this 35 days ago, and no pull request is open. OpenDCO website Windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Document Real Address format change in management/status output (OpenVPN 2.7)Possibly taken A pull request linked to this issue is open or already merged. Opendocumentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Since 2.7.9 "route-method exe" can't set routePossibly taken @d12fk claimed this 1 day ago. Openoutdated code Windows
-
enhancement feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
issue: bug report
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Stellarium/stellarium#5197 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ChupathingyCE/chupathingyce#1550 ·
Maintainers usually reply within 1 day
-
[BUG] SWAPDB sends no invalidation to CLIENT TRACKING clientsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
redis/redis#16302 · 1 comment ·
Maintainers usually reply within 1 day