OpenVPN/openvpn

test environment: test --persist-tun with ping-timeout

Open

#948 建立於 2025年12月30日

在 GitHub 查看
 (1 留言) (1 反應) (6 負責人)C (13,839 star) (3,314 fork)batch import
DCOenhancementfeaturehelp wanted

描述

So what we lack testing for is ping-timeout reconnects with DCO involved

  • --client side
  • connect
  • ping-timeout (30s) (triggerable via kill $CN on the server's management interface, or possibly via firewall rule in between - though timing is complicated if you want reconnect to succeed)
  • reconnect
  • ping-timeout again (30s)
  • eventually tls-renegotiate (300s)

and verify that pings through the tunnel are working all the time as one would expect this - fail while the server's instance is dead, but do not fail longer than 30-ish seconds.

Maybe also check the server's idea of "when did the client reconnect?" - which gives a good indication of "did ping-timeout actually work?".

The issue at hand is on FreeBSD, but I guess that having test coverage on Linux and Windows won't hurt either...

貢獻者指南

技術棧
cshell
領域
testingsecuritybackend
議題類型
test
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
OpenVPN build systemDCO understandingnetwork mockingtest infrastructure
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
The issue requests adding a test scenario for persist tun with ping timeout and DCO. It describes client side steps: connect, trigger ping timeout via server disconnect, verify reconnect and tunnel continuity. The test should also check server side reconnection timestamps. Implementation likely involves modifying existing test scripts in the 'tests' directory, possibly adding a new test suite in 'tests/unit tests' or 'tests/t client.sh'. Review linked PRs and comments for any existing work; as of now, no PRs are linked. Focus on understanding OpenVPN's DCO behavior and the test framework (likely cmocka or similar) before writing the test.