DCO-Win: explicit-exit-notify is dropped when using DC

Aperta
#1,118 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c
Ambito
networking

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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!

Lingua principale
C
Stelle
14.8k
Fork
3.4k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenVPN/openvpn

Tutte le issue di OpenVPN/openvpn

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.