OpenVPN 2.7.6 compatibility regression with MikroTik RouterOS clients – HARD_RESET_CLIENT_V2 packet ID 1 rejected
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- c
- Domain
- networking
Research direction
Begin with the OpenVPN 2.7.6 validation path for P_CONTROL_HARD_RESET_CLIENT_V2 and compare it with 2.7.5, using the supplied TCP logs or RouterOS clients to reproduce packet ID 1. Done means determining whether a compatibility mode is safe and defining a migration path without changing the stricter default.
Written by the indexing model from the issue text.
Description
Hello OpenVPN developers,
I would like to report a compatibility regression observed after upgrading an OpenVPN server to OpenVPN 2.7.6.
The affected clients are MikroTik routers using the built-in RouterOS OpenVPN client.
Server environment
- OS: Debian 13 (Trixie)
- OpenVPN: 2.7.6-trixie1
- Architecture: amd64
- Package repository: official OpenVPN 2.7 Debian repository (
build.openvpn.net) - Transport: TCP
Installed package:
openvpn:
Installed: 2.7.6-trixie1
Candidate: 2.7.6-trixie1
The following previous releases are also available from the same repository:
2.7.5-trixie1
2.7.4-trixie1
2.7.3-trixie1
...
Problem
After upgrading to OpenVPN 2.7.6, multiple MikroTik RouterOS OpenVPN clients can establish a TCP connection to the server, but cannot proceed with the OpenVPN TLS handshake.
The server reports:
2026-08-21 13:58:49 TCP connection established with [AF_INET]WWW.XXX.YYY.ZZZ:34021
2026-08-21 13:58:49 tcp4-server:WWW.XXX.YYY.ZZZ:34021 TLS Error: received P_CONTROL_HARD_RESET_CLIENT_V2 with packet id 1 from [AF_INET]WWW.XXX.YYY.ZZZ:34021 -- 0 was expected, ignoring packet
2026-08-21 13:58:49 TCP connection established with [AF_INET]WWW.XXX.YYY.ZZZ:11444
2026-08-21 13:58:49 tcp4-server:WWW.XXX.YYY.ZZZ:11444 TLS Error: received P_CONTROL_HARD_RESET_CLIENT_V2 with packet id 1 from [AF_INET]WWW.XXX.YYY.ZZZ:11444 -- 0 was expected, ignoring packet
2026-08-21 13:58:49 tcp4-server:WWW.XXX.YYY.ZZZ:55386 TLS Error: received P_CONTROL_HARD_RESET_CLIENT_V2 with packet id 1 from [AF_INET]WWW.XXX.YYY.ZZZ:55386 -- 0 was expected, ignoring packet
This behavior is reproducible with multiple independent MikroTik clients.
All of them appear to send:
P_CONTROL_HARD_RESET_CLIENT_V2
packet id = 1
while OpenVPN 2.7.6 requires:
packet id = 0
The packet is therefore ignored before the TLS handshake can proceed.
OpenVPN 2.7.6 behavior change
As I understand it, OpenVPN 2.7.6 introduced stricter validation of HARD_RESET packets and now rejects a HARD_RESET packet when its sequence/packet ID is not 0.
This appears to be correct according to the expected OpenVPN protocol behavior.
However, existing MikroTik RouterOS OpenVPN clients appear to have been sending the initial HARD_RESET packet with ID 1, which was tolerated by previous OpenVPN releases.
As a result, upgrading an existing OpenVPN server to 2.7.6 can cause all affected MikroTik RouterOS OpenVPN clients to stop connecting immediately.
Expected / previous behavior
Previous OpenVPN server releases tolerated the MikroTik client's:
P_CONTROL_HARD_RESET_CLIENT_V2 packet id 1
allowing the handshake to continue.
OpenVPN 2.7.6 behavior
OpenVPN 2.7.6 rejects it with:
TLS Error: received P_CONTROL_HARD_RESET_CLIENT_V2 with packet id 1 ... -- 0 was expected, ignoring packet
This prevents the connection from reaching the TLS certificate verification stage.
Current workaround
Downgrading the OpenVPN server from:
2.7.6-trixie1
to:
2.7.5-trixie1
is currently being considered as a compatibility workaround.
There does not appear to be a server configuration option in OpenVPN 2.7.6 to disable only this new HARD_RESET packet-ID validation.
Options related to certificate verification, replay protection, or general compatibility do not appear to control this check.
Questions / request
I understand that sending a HARD_RESET packet with ID 1 may be incorrect behavior on the MikroTik side, and I am also reporting the issue to MikroTik.
However, considering that existing deployed RouterOS clients apparently relied on the behavior accepted by previous OpenVPN releases, could you please clarify:
-
Is rejecting
P_CONTROL_HARD_RESET_CLIENT_V2with packet ID1intentional and mandatory behavior in OpenVPN 2.7.6? -
Is there currently any configuration option or
compat-modesetting that can restore the pre-2.7.6 behavior temporarily? -
If not, would you consider adding a temporary compatibility option allowing non-zero HARD_RESET packet IDs for legacy/third-party clients?
-
Are there security implications that make retaining the previous tolerant behavior unacceptable?
The goal would not be to change the default behavior, but to provide administrators with a migration path for existing MikroTik RouterOS deployments until the client implementation is fixed.
I can provide additional server logs, configuration details, and packet captures if needed.
ROS: 6.49.20 and 7.23.3
- 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